Each remoteproc might have different requirements for coredumps and might
want to choose the type of dumps it wants to collect. This change allows
remoteproc drivers to specify their own custom dump function to be executed
in place of rproc_coredump. If the coredump op is not specified by the
This patch adds support for collecting minidump in the
event of remoteproc crash. Parse the minidump table
based on remoteproc's unique minidump-id, read all
memory regions from the remoteproc's minidump table
entry and expose the memory to userspace.
The remoteproc platform driver can choose to
Sometimes firmware sizes can be in ten's of MB's and reading
all the memory during coredump can consume lot of time and
memory.
Introducing support for mini-dumps. Mini-dump contains smallest
amount of useful information, that could help to debug subsystem
crashes.
During bootup memory is
Convert driver to use watchdog subsystem.
RFC/RFT: Completely untested. Also see FIXME comments in code.
Notes:
- The driver no longer uses platform data.
Using resources to pass PCI configuration register addresses
does not make much sense, and the PCI device can be obtained
with
misc pile; there's more locally, but the rest hadn't sat in -next,
so... No common topic whatsoever in those, sorry.
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the git repository at:
The following changes since commit f073531070d24bbb82cb2658952d949f4851024b:
init: add an init_dup helper (2020-08-04 21:02:38 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes
for you to fetch changes up to
Hi Florian,
On 8/7/20 1:09 PM, Florian Fainelli wrote:
>
> On 8/7/2020 12:08 PM, Guenter Roeck wrote:
>> On 8/7/20 11:08 AM, Florian Fainelli wrote:
>>>
>>>
>>> On 8/7/2020 9:21 AM, Guenter Roeck wrote:
On Fri, Aug 07, 2020 at 04:59:02PM +0530, madhuparnabhowmi...@gmail.com
wrote:
TAdut4 was calculated each iteration although it did not change. In light
of near future additions of the Extended range DSP calculations, this
function refactoring will help reduce unrelated changes in that series as
well as reduce the number of new functions needed.
Signed-off-by: Crt Mori
---
Since the second patch is dependent on the first and was still not
merged, I have decided to send them together. First patch just makes
second one more readable as it splits out the repeated calculation and
that enables the second patch to tweak the variable to the new
condition.
Crt Mori (2):
For some time the market wants medical grade accuracy in medical range,
while still retaining the declared accuracy outside of the medical range
within the same sensor. That is why we created extended calibration
which is automatically switched to when object temperature is too high.
This patch
On Tue, Aug 4, 2020 at 5:23 AM Vikash Garodia <"Vikash
Garodia"@qti.qualcomm.com> wrote:
>
> From: Vikash Garodia
>
> There are few list handling issues while adding and deleting
> node in the registered buf list in the driver.
> 1. list addition - buffer added into the list during buf_init
>
On 07/08/2020 20:12, Linus Torvalds wrote:
> On Fri, Aug 7, 2020 at 11:06 AM Daniel Lezcano
> wrote:
>>
>> Ok, I will send a fix.
>
> I ended up doing it during my morning routine of looking around for,
> and applying, random patches.
>
> So it's commit 0f5d0a4c01cc ("thermal: don't make
x86 and arm64 can both support direct access of event counters in
userspace. The access sequence is less than trivial and currently exists
in perf test code (tools/perf/arch/x86/tests/rdpmc.c) with copies in
projects such as PAPI and libpfm4.
Patches to add arm64 userspace support are pending[1].
On Fri, Aug 07, 2020 at 03:49:39PM -0700, Lokesh Gidra wrote:
> The new functions accept an optional context_inode parameter that
> callers can use to provide additional contextual information to
> security modules, e.g., indicating that one anonymous struct file is a
> logical child of another,
On Fri, 7 Aug 2020 at 13:13, Crt Mori wrote:
>
> On Fri, 7 Aug 2020 at 12:29, Andy Shevchenko
> wrote:
> >
> > On Fri, Aug 7, 2020 at 12:21 PM Crt Mori wrote:
> >
> > Oh yeah, you are right, there will be some comments :-)
> >
>
> Told ya. No matter how many times I go through it, I always
Hi Linus,
Please pull the power-supply changes for the 5.9 development cycle.
Stephen mentioned one trivial merge conflict between the
power-supply tree and the set_fs tree and has the correct solution:
https://lore.kernel.org/linux-next/20200727210137.01a5d...@canb.auug.org.au/
The following
R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this
remotproc driver, we can boot the R5 sub-system in different
configurations.
Signed-off-by: Ben Levinsky
Signed-off-by: Wendy Liang
Signed-off-by: Michal Simek
Signed-off-by: Ed Mooring
Signed-off-by: Jason Wu
---
v2:
-
On Tue, Aug 04, 2020 at 12:40:47PM -0700, Sean V Kelley wrote:
> From: Jonathan Cameron
>
> Currently the kernel does not handle AER errors for Root Complex integrated
> End Points (RCiEPs)[0]. These devices sit on a root bus within the Root
> Complex
> (RC). AER handling is performed by a Root
From: Daniel Colascione
This change uses the anon_inodes and LSM infrastructure introduced in
the previous patch to give SELinux the ability to control
anonymous-inode files that are created using the new _secure()
anon_inodes functions.
A SELinux policy author detects and controls these
From: Daniel Colascione
This change gives userfaultfd file descriptors a real security
context, allowing policy to act on them.
Signed-off-by: Daniel Colascione
[Remove owner inode from userfaultfd_ctx]
[Use anon_inode_getfd_secure() instead of anon_inode_getfile_secure()
in userfaultfd
From: Daniel Colascione
This change adds two new functions, anon_inode_getfile_secure and
anon_inode_getfd_secure, that create anonymous-node files with
individual non-S_PRIVATE inodes to which security modules can apply
policy. Existing callers continue using the original singleton-inode
kind
Userfaultfd in unprivileged contexts could be potentially very
useful. We'd like to harden userfaultfd to make such unprivileged use
less risky. This patch series allows SELinux to manage userfaultfd
file descriptors and in the future, other kinds of
anonymous-inode-based file descriptor. SELinux
On Fri, Aug 7, 2020 at 9:16 AM Alan Maguire wrote:
>
> On Thu, 6 Aug 2020, Uriel Guajardo wrote:
>
> > Adds an API to allow dynamic analysis tools to fail the currently
> > running KUnit test case.
> >
> > - Always places the kunit test in the task_struct to allow other tools
> > to access the
On 8/7/20 9:48 AM, Kirill A. Shutemov wrote:
[...]
+static inline int head_mapcount(struct page *head)
+{
Do we want VM_BUG_ON_PAGE(!PageHead(head), head) here?
Well, no. That was the point of the bug report -- by the time we called
compound_mapcount, the page was no longer a head page.
On 8/7/20 2:12 AM, Wei Yang wrote:
> Following are some cleanup for hugetlb.
>
> Simple test with tools/testing/selftests/vm/map_hugetlb pass.
>
> Wei Yang (10):
> mm/hugetlb: not necessary to coalesce regions recursively
> mm/hugetlb: make sure to get NULL when list is empty
> mm/hugetlb:
On Thu, Aug 06, 2020 at 10:09:41AM +0200, Ingo Molnar wrote:
* Sasha Levin wrote:
Hi Linus,
Please consider applying these patches for liblockdep, or alternatively
pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git
tags/liblockdep-fixes-040820
The patches fix up
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5631c5e0eb9035d92ceb20fcd9cdb7779a3f5cc7
commit: 00720f0e7f288d29681d265c23b22bb0f0f4e5b4 smack: avoid unused 'sip'
variable warning
date: 3 months ago
config: s390-randconfig-s032-20200808 (attached as
On Fri, Aug 07, 2020 at 01:29:24PM -0700, John Stultz wrote:
> On Thu, Jul 9, 2020 at 11:28 AM Kees Cook wrote:
> >
> > Duplicate the cleanups from commit 2618d530dd8b ("net/scm: cleanup
> > scm_detach_fds") into the compat code.
> >
> > Replace open-coded __receive_sock() with a call to the
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
tags/pci-v5.9-changes
for you to fetch changes up to
When i2c client unregisters, synchronize irq before setting
iproc_i2c->slave to NULL.
(1) disable_irq()
(2) Mask event enable bits in control reg
(3) Erase slave address (avoid further writes to rx fifo)
(4) Flush tx and rx FIFOs
(5) Clear pending event (interrupt) bits in status reg
(6)
> On Aug 7, 2020, at 2:02 PM, ty...@mit.edu wrote:
>
> Thanks, applied, although I rewrote the commit description to make it
> be a bit more clearer:
>
>fs: prevent BUG_ON in submit_bh_wbc()
>
>If a device is hot-removed --- for example, when a physical device is
>unplugged from
On Mon, Aug 03, 2020 at 04:17:44PM +, Lazar Beloica wrote:
> When FTRIM is issued on a group, ext4 marks it as trimmed so another FTRIM
> on the same group has no effect. Ext4 marks group as trimmed if at least
> one block is trimmed, therefore it is possible that a group is marked as
>
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net/master]
url:
https://github.com/0day-ci/linux/commits/min-li-xe-renesas-com/ptp-ptp_idt82p33-update-to-support-adjphase/20200808-000545
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
On Fri, Aug 7, 2020 at 2:29 PM Arvind Sankar wrote:
>
> On Fri, Aug 07, 2020 at 12:41:00PM -0700, Nick Desaulniers wrote:
> > A recent change to a default value of configuration variable
> > (ENABLE_X86_RELAX_RELOCATIONS OFF -> ON) in LLVM now causes Clang's
> > integrated assembler to emit
On Fri, Aug 7, 2020 at 6:10 AM Kalyan Thota wrote:
>
> In TEST_ONLY commit, rm global_state will duplicate the
> object and request for new reservations, once they pass
> then the new state will be swapped with the old and will
> be available for the Atomic Commit.
>
> This patch fixes some of
Quoting Stephen Boyd (2020-06-11 15:46:58)
> Quoting Sandeep Maheswaram (2020-06-11 07:28:02)
> > From: Taniya Das
> >
> > The USB client requires the usb30_prim gdsc to be kept active for
> > certain use cases, thus add the GENPD_FLAG_ACTIVE_WAKEUP flag.
>
> Can you please describe more of
Quoting Taniya Das (2020-08-05 22:23:05)
> On 8/6/2020 1:54 AM, Stephen Boyd wrote:
> >> + .hw = _clk_src.clkr.hw,
> >> + },
> >> + .num_parents = 1,
> >> + .flags = CLK_SET_RATE_PARENT,
> >> +
Since I'm almost certain I didn't get capability checking right for
pre-volta chipsets, let's start logging any caps we find to make things
like this obvious in the future.
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/nouveau/dispnv50/disp.c | 10 ++
1 file changed, 10 insertions(+)
Not entirely sure why this never came up when I originally tested this
(maybe some BIOSes already have this setup?) but the ->caps_init vfunc
appears to cause the display engine to throw an exception on driver
init, at least on my ThinkPad P72:
nouveau :01:00.0: disp: chid 0 mthd 008c data
On Thu, Aug 6, 2020 at 5:53 PM Andy Shevchenko
wrote:
>
> On Thu, Aug 6, 2020 at 12:48 PM Arpitha Raghunandan <98.a...@gmail.com> wrote:
> >
> > Converts test lib/test_hexdump.c to KUnit.
> > More information about KUnit can be found at
> >
Add a simple mechanism for exporting percpu data through metricfs.
The API follows the existing metricfs pattern. A percpu file is
defined with:
METRIC_EXPORT_PERCPU_INT(name, desc, fn)
METRIC_EXPORT_PERCPU_COUNTER(name, desc, fn)
The first defines a file for exposing a percpu int. The
Count kernel warnings by function name of the caller.
Each time WARN() is called, which includes WARN_ON(), increment a counter
in a 256-entry hash table. The table key is the entry point of the calling
function, which is found using kallsyms.
We store the name of the function in the table
Add metricfs support for displaying percpu scheduler counters.
The top directory is /sys/kernel/debug/metricfs/stat (analogous
to /proc/stat). Then there is a subdirectory for each scheduler
stat. For example:
cat /sys/kernel/debug/metricfs/stat/user/values
Signed-off-by: Jonathan Adams
From: Laurent Chavey
Export /proc/net/dev statistics via metricfs.
The implementation reports all the devices that are in the same
network namespace as the process reading metricfs.
The implementation does not report devices across network namespaces
Signed-off-by: Laurent Chavey
Add metricfs support for displaying percpu irq counters for x86.
The top directory is /sys/kernel/debug/metricfs/irq_x86.
Then there is a subdirectory for each x86-specific irq counter.
For example:
cat /sys/kernel/debug/metricfs/irq_x86/TLB/values
Signed-off-by: Jonathan Adams
---
On Thu, 6 Aug 2020 13:54:31 +0100, Jon Hunter wrote:
> Following commit d8f090dbeafd ("rtc: max77686: Do not allow interrupt to
> fire before system resume"), RTC wake-ups stopped working on Jetson TX2
> and Jetson Xavier platforms. The Jetson TX2 uses the max77620 PMIC and
> the Jetson Xavier
Add metricfs support for displaying percpu softirq counters. The
top directory is /sys/kernel/debug/metricfs/softirq. Then there
is a subdirectory for each softirq type. For example:
cat /sys/kernel/debug/metricfs/softirq/NET_RX/values
Signed-off-by: Jonathan Adams
---
On Thu, Jul 30, 2020 at 4:47 AM Stanimir Varbanov
wrote:
>
> Presently the recovery mechanism is using two hfi functions
> to destroy and create interface queues. For the purpose of
> recovery we don't need to free and allocate the memory used
> for interface message queues, that's why we
From: Justin TerAvest
Metricfs is a standardized set of files and directories under debugfs,
with a kernel API designed to be simpler than exporting new files under
sysfs. Type and field information is reported so that a userspace daemon
can easily process the information.
The statistics live
[resending to widen the CC lists per rdun...@infradead.org's suggestion
original posting to lkml here: https://lkml.org/lkml/2020/8/5/1009]
To try to restart the discussion of kernel statistics started by the
statsfs patchsets (https://lkml.org/lkml/2020/5/26/332), I wanted
to share the following
On Fri, Aug 07, 2020 at 12:41:00PM -0700, Nick Desaulniers wrote:
> A recent change to a default value of configuration variable
> (ENABLE_X86_RELAX_RELOCATIONS OFF -> ON) in LLVM now causes Clang's
> integrated assembler to emit R_X86_64_GOTPCRELX/R_X86_64_REX_GOTPCRELX
> relocations. LLD will
On Thu, Jul 30, 2020 at 4:47 AM Stanimir Varbanov
wrote:
>
> After power domains and clock restructuring the recovery for
> sdm845 and v4 did not work properly. Fix that by reworking the
> recovery function and the sequence.
>
> Signed-off-by: Stanimir Varbanov
> ---
>
On Fri, Aug 07, 2020 at 09:50:55AM -0700, Randy Dunlap wrote:
> Drop repeated words in comments.
> {a, then, to}
>
> Signed-off-by: Randy Dunlap
> Cc: John Johansen
> Cc: appar...@lists.ubuntu.com
> Cc: James Morris
> Cc: "Serge E. Hallyn"
> Cc: linux-security-mod...@vger.kernel.org
On Thu, Jul 30, 2020 at 4:47 AM Stanimir Varbanov
wrote:
>
> Presently the hfi_parser has been called only once during driver
> probe. To prepare the parser function to be called multiple times
> from recovery we need to initialize few variables which are used
> during parsing time.
>
>
[ This time Cc'ing LKML ]
Linus,
Tracing updates for 5.9
- The biggest news in that the tracing ring buffer can now time events that
interrupted other ring buffer events. Before this change, if an interrupt
came in while recording another event, and that interrupt also had an
event,
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5631c5e0eb9035d92ceb20fcd9cdb7779a3f5cc7
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 7 weeks ago
config: arm-randconfig-s032-20200808 (attached
On Tue, Aug 04, 2020 at 11:33:51AM +0200, dan...@ffwll.ch wrote:
> On Sat, Aug 01, 2020 at 04:30:23PM -0300, Melissa Wen wrote:
> > On Wed, Jul 29, 2020 at 12:22 PM Sidong Yang wrote:
> > >
> > > This patch modifies function call sequence in commit tail. This is for
> > > the problem that raised
Hello,
syzbot found the following issue on:
HEAD commit:fffe3ae0 Merge tag 'for-linus-hmm' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1194d90a90
kernel config: https://syzkaller.appspot.com/x/.config?x=18bb86f2e4ebfda2
Hopefully the last patch for this merge window pull request.
-- Steve
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 38ce2a9e33db61a3041840310077072d6210ead4
Steven Rostedt (VMware) (1):
tracing: Add trace_array_init_printk() to initialize
8912fd6a61d7474ea9b43be93f136034d28868d5
config: i386-randconfig-s001-20200807 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-118-ge1578773-dirty
# save the attached .config to linux build tree
Gabriel Krisman Bertazi writes:
> The following changes since commit 9c94b39560c3a013de5886ea21ef1eaf21840cb9:
>
> Merge tag 'ext4_for_linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2020-04-05 10:54:03
> -0700)
>
Hi Ted,
Sorry for the ping, I understand you are extra
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5631c5e0eb9035d92ceb20fcd9cdb7779a3f5cc7
commit: 3f649ab728cda8038259d8f14492fe400fbab911 treewide: Remove
uninitialized_var() usage
date: 3 weeks ago
config: x86_64-randconfig-m031-20200807 (attached
The pull request you sent on Fri, 7 Aug 2020 01:30:04 -0500:
> git://git.linaro.org/landing-teams/working/fujitsu/integration.git
> tags/mailbox-v5.9
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/75dee3b6de4ce31464ffb827b81ddb5414599159
Thank you!
--
The pull request you sent on Fri, 7 Aug 2020 11:35:51 +0530:
> git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git
> tags/dmaengine-5.9-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ce615f5c1f73537c8267035d58b3d0c70e19b8da
Thank you!
--
The pull request you sent on Fri, 7 Aug 2020 12:46:11 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
> tags/seccomp-v5.9-rc1-fix1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1fa2c0a0c814fbae0eb3e79a510765225570d043
Thank you!
--
The pull request you sent on Fri, 7 Aug 2020 12:55:32 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
> tags/kallsyms_show_value-fix-v5.9-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6ba0d2e4fc2f3e8544f40fb1165c668f78fe951c
Thank you!
The pull request you sent on Fri, 7 Aug 2020 13:02:19 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
> tags/clk-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/30185b69a2d533c4ba6ca926b8390ce7de495e29
Thank you!
--
Deet-doot-dot,
The pull request you sent on Fri, 7 Aug 2020 20:06:01 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-5.9-rc1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f6235eb189706bf38c82b5fa5f2db0d21bc1dcef
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 7 Aug 2020 20:36:57 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.fdpic
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0f43283be7fec4a76cd4ed50dc37db30719bde05
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 7 Aug 2020 10:42:58 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
> tags/media/v5.9-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fa73e212318a3277ae1f304febbc617c75d4d2db
Thank you!
--
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5631c5e0eb9035d92ceb20fcd9cdb7779a3f5cc7
commit: 3f649ab728cda8038259d8f14492fe400fbab911 treewide: Remove
uninitialized_var() usage
date: 3 weeks ago
config: i386-randconfig-m021-20200807 (attached
On Fri, 07 Aug 2020 21:23:39 +0200
Peter Zijlstra wrote:
> The lockdep tracepoints are under the lockdep recursion counter, this
> has a bunch of nasty side effects:
>
> - TRACE_IRQFLAGS doesn't work across the entire tracepoint, leading to
>all sorts of dodgy complaints.
>
> -
On 8/7/2020 11:39 AM, Jason Gunthorpe wrote:
On Fri, Aug 07, 2020 at 10:54:51AM -0700, Dey, Megha wrote:
So from the hierarchical domain standpoint, we will have:
- For DSA device: vector->intel-IR->IDXD
- For Jason's device: root domain-> domain A-> Jason's device's IRQ domain
- For any
- On Aug 7, 2020, at 2:47 PM, Peter Oskolkov p...@posk.io wrote:
> On Fri, Aug 7, 2020 at 11:25 AM Mathieu Desnoyers
> wrote:
>>
>> - On Aug 7, 2020, at 1:55 PM, Peter Oskolkov p...@posk.io wrote:
>>
>> > On Thu, Aug 6, 2020 at 5:27 PM Boqun Feng wrote:
>> [...]
>> >> What if the
On Thu, Jul 9, 2020 at 11:28 AM Kees Cook wrote:
>
> Duplicate the cleanups from commit 2618d530dd8b ("net/scm: cleanup
> scm_detach_fds") into the compat code.
>
> Replace open-coded __receive_sock() with a call to the helper.
>
> Move the check added in commit 1f466e1f15cf ("net: cleanly handle
On 8/7/20 1:24 PM, Stephen Boyd wrote:
> Quoting Rob Clark (2020-08-07 08:51:48)
>> On Fri, Aug 7, 2020 at 8:27 AM Randy Dunlap wrote:
>>>
>>> On 8/7/20 12:17 AM, Tanmay Shah wrote:
diff --git a/drivers/gpu/drm/msm/Kconfig b/drivers/gpu/drm/msm/Kconfig
index ea3c4d094d09..cc1392b29022
Quoting Rob Clark (2020-08-07 08:51:48)
> On Fri, Aug 7, 2020 at 8:27 AM Randy Dunlap wrote:
> >
> > On 8/7/20 12:17 AM, Tanmay Shah wrote:
> > > diff --git a/drivers/gpu/drm/msm/Kconfig b/drivers/gpu/drm/msm/Kconfig
> > > index ea3c4d094d09..cc1392b29022 100644
> > > ---
[+cc Jean for i801 question below]
On Thu, Aug 06, 2020 at 01:06:16AM +0530, Vaibhav Gupta wrote:
> Drivers using legacy power management .suspen()/.resume() callbacks
> have to manage PCI states and device's PM states themselves. They also
> need to take care of standard configuration registers.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5631c5e0eb9035d92ceb20fcd9cdb7779a3f5cc7
commit: 57a10d8c1123068e3cb06434fbc9634f945d3062 ptp: Add a ptp clock driver
for IDT 82P33 SMU.
date: 6 months ago
compiler: powerpc64-linux-gcc (GCC) 9.3.0
If
Hi Sergei,
Thank you for the review.
On Fri, Aug 7, 2020 at 8:48 PM Sergei Shtylyov
wrote:
>
> Hello!
>
> On 8/7/20 8:49 PM, Lad Prabhakar wrote:
>
> > Add du node to r8a7742 SoC DT. Boards that want to enable the DU
>
> Both "du" and "DU" on a single line? :-)
>
Argh my bad.
Cheers,
On Fri, 07 Aug 2020 21:23:38 +0200
Peter Zijlstra wrote:
> Much of the complexity in irqenter_{enter,exit}() is due to #PF being
> the sole exception that can schedule from kernel context.
>
> One additional wrinkle with #PF is that it is non-maskable, it can
> happen _anywhere_. Due to this,
Hi Larent/Geert/Niklas,
On Wed, Aug 5, 2020 at 1:35 PM Laurent Pinchart
wrote:
>
> Hi Geert,
>
> On Wed, Aug 05, 2020 at 10:43:25AM +0200, Geert Uytterhoeven wrote:
> > On Wed, Aug 5, 2020 at 10:01 AM Lad, Prabhakar wrote:
> > > On Tue, Aug 4, 2020 at 4:32 PM Geert Uytterhoeven wrote:
> > >> On
On Fri, Aug 07, 2020 at 11:12:29AM -0700, Nick Desaulniers wrote:
> On Fri, Jul 31, 2020 at 4:08 PM Kees Cook wrote:
> >
> > From: Arvind Sankar
> >
> > The BFD linker generates run-time relocations for z_input_len and
> > z_output_len, even though they are absolute symbols.
> >
> > This is
Quoting Rohit Kumar (2020-08-05 20:59:48)
> Thanks Stephen for reviewing.
>
> On 8/6/2020 6:01 AM, Stephen Boyd wrote:
> > Quoting Rohit kumar (2020-07-22 03:31:44)
> >> From: Ajit Pandey
> >>
> >> LPASS variants have their own soc specific clocks that needs to be
> >> enabled for MI2S audio
On 8/7/20 1:55 PM, Kees Cook wrote:
Hi Linus,
Please pull this fix to my kallsyms_show_value() refactoring for
v5.9-rc1. About a month after the original refactoring landed, 0day
noticed that there was a path through the kernfs binattr read handlers
that did not have PAGE_SIZEd buffers, and the
The vfio_iommu_replay() function does not currently unwind on error,
yet it does pin pages, perform IOMMU mapping, and modify the vfio_dma
structure to indicate IOMMU mapping. The IOMMU mappings are torn down
when the domain is destroyed, but the other actions go on to cause
trouble later. For
On Fri, Aug 7, 2020 at 10:21 AM Jianlin Lv wrote:
>
> test_progs reports the segmentation fault as below
>
> $ sudo ./test_progs -t mmap --verbose
> test_mmap:PASS:skel_open_and_load 0 nsec
> ..
> test_mmap:PASS:adv_mmap1 0 nsec
> test_mmap:PASS:adv_mmap2 0 nsec
> test_mmap:PASS:adv_mmap3 0
dynamic-debug metadata is bloated; the __dyndbg linker section is
effectively an array of struct _ddebugs, and its 1st 3 members are
highly repetetive, with 90%, 84%, 45% repeats. Total reported usage
~150kb for ~2600 callsites on my laptop config.
This patchset is one diet plan. it all holds
Split the struct into 2 linked parts (head & body) so that next,
struct _ddebug_callsite can be off-lined to zram, and only mapped in
as needed. The split increases overall memory use by 1 pointer per
callsite, but 4 pointers and a short are now 99% likely to be off-line
(once implemented), and
this throwaway patch demonstrates the extra weight:
dyndbg: 2605 entries. repeated entries: 2369 module 2231 file 1147 func
Thats (91%, 86%, 44%) repeated values in those pointers/columns.
This simple test also shows that a similarly simple run-length encoder
on those 3 columns would compress
dyndbg will next need zs_malloc and friends, so add config reqs now,
to avoid touching make-deps late in a patch-set.
I used select in order not to hide dyndbg inadvertently.
I want to say recommends, since it could be an optional feature.
Whats the best way ?
Signed-off-by: Jim Cromie
---
This commit doesnt improve things, last commit was working, next one
still breaks, despite this "fix". I keep it separate for the
following review, which now stated, will be refuted as needed. ;-)
Locking review:
ddebug_zpool_init(), like other *_init() routines, does no locking
itself. Unlike
HEAD~1 split struct _ddebugs into heads & bodies, linked accross 2 ELF
sections. Lets now store copies of the bodies into a zs_pool, and
relink head to the new body. This should allow recycling the section
soon.
The strategy is to let a compression algo handle the repetition, and
map individual
Specify the print-width so log entries line up nicely.
no functional changes.
Signed-off-by: Jim Cromie
---
lib/dynamic_debug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index 1d012e597cc3..01b7d0210412 100644
---
add ddebug_zpool_remove() to undo ddebug_zpool_add(), and call it from
ddebug_remove_module().
Signed-off-by: Jim Cromie
---
lib/dynamic_debug.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index 049299027fb3..102f47b2a439
in ddebug_zpool_put() dont zs_unmap the callsite, if it is enabled for
printing. This will eliminate possibly repeated un-maps then re-maps
of enabled and invoked pr-debug callsites, and will promptly retire
all other uses.
But this causes kernel to BUG
[1.364303] BUG: sleeping function
summary: no fix here.
Locking review:
ddebug_zpool_init(), like other *_init() routines, does not run under
a lock (that we control). Unlike them, it runs later, at late_init.
I dont know whether this is pertinent to the kernel panic.
ddebug_callsite_get/put() are called as a pair under
On 8/7/2020 12:08 PM, Guenter Roeck wrote:
> On 8/7/20 11:08 AM, Florian Fainelli wrote:
>>
>>
>> On 8/7/2020 9:21 AM, Guenter Roeck wrote:
>>> On Fri, Aug 07, 2020 at 04:59:02PM +0530, madhuparnabhowmi...@gmail.com
>>> wrote:
From: Madhuparna Bhowmik
In rdc321x_wdt_probe(),
On Wed, Aug 05, 2020 at 09:44:45AM -0400, Michael S. Tsirkin wrote:
> Virtio pmem is modern-only. Use LE accessors for config space.
>
> Signed-off-by: Michael S. Tsirkin
> ---
> drivers/nvdimm/virtio_pmem.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On Mon, Aug 3, 2020 at 12:36 PM Jordan Crouse wrote:
>
> Add support for allocating private address space instances. Targets that
> support per-context pagetables should implement their own function to
> allocate private address spaces.
>
> The default will return a pointer to the global address
101 - 200 of 954 matches
Mail list logo
