On Sat, 28 Nov 2020 at 04:26, Hemant Kumar wrote:
>
> This MHI client driver allows userspace clients to transfer
> raw data between MHI device and host using standard file operations.
> Driver instantiates UCI device object which is associated to device
> file node. UCI device object
On 15/09/20 00:13, Sean Christopherson wrote:
+static void kvm_post_set_cr0(struct kvm_vcpu *vcpu, unsigned long old_cr0,
+unsigned long cr0)
What about using __kvm_set_cr*() instead of kvm_post_set_cr*()? That would
show that __kvm_set_cr*() is a subordinate of
On Mon, Nov 30, 2020 at 10:05 AM Russell King - ARM Linux admin
wrote:
>
> If you think that /dev/sda for example is always the machine's internal
> HDD, that is wrong.
Yes. See the whole part about
"Note that it really is only the internal devices that matter. Once you
start plugging in an
On Sat, Nov 28, 2020 at 08:23:59AM -0800, Yu, Yu-cheng wrote:
> We have X86_BRANCH_TRACKING_USER too. My thought was, X86_CET means any of
> kernel/user shadow stack/ibt.
It is not about what it means - it is what you're going to use/need. You have
ifdeffery both with X86_CET and
On Mon, Nov 30, 2020, Paolo Bonzini wrote:
> On 16/09/20 02:19, Sean Christopherson wrote:
> >
> > TDX also selectively blocks/skips portions of other ioctl()s so that the
> > TDX code itself can yell loudly if e.g. .get_cpl() is invoked. The event
> > injection restrictions are due to direct
On Mon, Nov 30, 2020 at 07:09:55PM +0200, Laurent Pinchart wrote:
> On Mon, Nov 30, 2020 at 01:31:24PM +, Daniel Scally wrote:
I agree with most of Laurent's comments. S
...
> > + Say Y here if your device is a detachable / hybrid laptop that comes
> > + with Windows installed by
On Tue, 2020-12-01 at 02:04 +0800, Kai-Heng Feng wrote:
> > On Dec 1, 2020, at 00:19, Srinivas Pandruvada <
> > srinivas.pandruv...@linux.intel.com> wrote:
> >
> > On Mon, 2020-11-30 at 16:23 +0800, Kai-Heng Feng wrote:
> > > > On Nov 30, 2020, at 15:57, Daniel Lezcano <
> > > >
On Mon, Nov 30, 2020 at 09:48:46AM -0500, Steven Rostedt wrote:
> On Thu, 26 Nov 2020 13:26:13 -0500
> Steven Rostedt wrote:
>
> > On Thu, 26 Nov 2020 06:52:45 +0100
> > Greg KH wrote:
> >
> > > On Tue, Nov 24, 2020 at 10:39:17PM +, J. Avila wrote:
> > > > Hello,
> > > >
> > > > In the
On 11/30/20 10:06 AM, Yu, Yu-cheng wrote:
>>> + if (!boot_cpu_has(X86_FEATURE_SHSTK) &&
>>> + !boot_cpu_has(X86_FEATURE_IBT))
>>> + xfeatures_mask_all &= ~BIT_ULL(i);
>>> + } else {
>>> + if ((xsave_cpuid_features[i] == -1) ||
>>
>> Where
From: Bean Huo
USFHCD supports WriteBooster "LU dedicated buffer” mode and
“shared buffer” mode both, so changes the comment in the
function ufshcd_wb_probe().
Signed-off-by: Bean Huo
---
drivers/scsi/ufs/ufshcd.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git
From: Bean Huo
Bean Huo (3):
scsi: ufs: Add "wb_on" sysfs node to control WB on/off
scsi: ufs: Keep device power on only
fWriteBoosterBufferFlushDuringHibernate == 1
scsi: ufs: Changes comment in the function ufshcd_wb_probe()
drivers/scsi/ufs/ufs-sysfs.c | 33
From: Bean Huo
Keep device power mode as active power mode and VCC supply only if
fWriteBoosterBufferFlushDuringHibernate setting 1 is successful.
Signed-off-by: Bean Huo
---
drivers/scsi/ufs/ufs.h| 2 ++
drivers/scsi/ufs/ufshcd.c | 11 ++-
2 files changed, 12 insertions(+), 1
From: Bean Huo
Currently we let UFS WriteBooster driver use clock scaling
up/down to set WB on/off, for the platform which doesn't
support UFSHCD_CAP_CLK_SCALING, WB will be always on. Provide
a sysfs attribute to enable/disable WB during runtime.
Signed-off-by: Bean Huo
---
Hi,
On Mon, Nov 30, 2020 at 9:44 AM Linus Torvalds
wrote:
>
> So basically, the way the async probing works for say SCSI is that we
> have multiple "layers of asynchroniety". We have the usual "init calls
> done asynchronously", but then within the init calls themselves you
> can start sub-scans
On Mon, Nov 30, 2020 at 12:07:17PM -0600, Pierre-Louis Bossart wrote:
> On 11/30/20 11:59 AM, Mark Brown wrote:
> > I'll drop this, hopefully it can be re-added in future.
> We fixed this problem in October, must be a patch that wasn't merged while
> upstreaming. If you give me 2-3 hours I can
On Fri, Nov 27, 2020 at 09:01:47AM +0800, Chao Yu wrote:
> On 2020/11/27 1:55, Eric Biggers wrote:
> > On Thu, Nov 26, 2020 at 06:37:09PM +0800, Chao Yu wrote:
> > > Support to use address space of inner inode to cache compressed block,
> > > in order to improve cache hit ratio of random read.
> >
On 11/29/20 7:20 PM, chenle...@gmail.com wrote:
> From: Lei Chen
>
> It's unnecessary to call wbt_update_limits explicitly within wbt_init,
> because it will be called in the following function wbt_queue_depth_changed.
Applied, thanks.
--
Jens Axboe
On Sat, Nov 28, 2020 at 5:02 PM Sonal Santan wrote:
>
> Hello,
>
> This patch series adds management physical function driver for Xilinx Alveo
> PCIe
> accelerator cards, https://www.xilinx.com/products/boards-and-kits/alveo.html
> This driver is part of Xilinx Runtime (XRT) open source stack.
>
On Mon, 30 Nov 2020 at 18:52, Nicolas Pitre wrote:
>
> On Mon, 30 Nov 2020, Ard Biesheuvel wrote:
>
> > On Mon, 30 Nov 2020 at 16:51, Nicolas Pitre wrote:
> >
> > > Here's my version of the fix which should be correct. Warning: this
> > > is completely untested, but should in theory produce the
On 11/30/20 11:59 AM, Mark Brown wrote:
On Fri, Nov 27, 2020 at 06:24:11PM +1100, Stephen Rothwell wrote:
Caused by commit
6f4a038b9967 ("ASoC/SoundWire: rt715-sdca: First version of rt715 sdw sdca codec
driver")
I have reverted that commit for today.
I'll drop this, hopefully it can
On 11/30/2020 9:45 AM, Dave Hansen wrote:
On 11/10/20 8:21 AM, Yu-cheng Yu wrote:
Control-flow Enforcement Technology (CET) adds five MSRs. Introduce
them and their XSAVES supervisor states:
MSR_IA32_U_CET (user-mode CET settings),
MSR_IA32_PL3_SSP (user-mode Shadow Stack pointer),
On Wed, Nov 4, 2020 at 9:53 AM 'Nick Desaulniers' via Clang Built
Linux wrote:
>
> Modifies CONFIG_DEBUG_INFO_DWARF4 to be a member of a choice. Adds an
> explicit CONFIG_DEBUG_INFO_DWARF2, which is the default. Does so in a
> way that's forward compatible with existing configs, and makes adding
On 2020-11-30 17:48, Rongwei Wang wrote:
The interfaces of this module is same as MSR module in user space, and
to solve
the problem that ARM platform has no similar MSR module. Using this
interface,
we did some pressure tests to test the stability and security of MSR
driver. The
test results
Hi Daniel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on driver-core/driver-core-testing pm/linux-next
v5.10-rc6 next-20201130]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
On Mon, Nov 30, 2020 at 09:44:03AM -0800, Linus Torvalds wrote:
> On Mon, Nov 30, 2020 at 9:04 AM Doug Anderson wrote:
> >
> > Without static assignment, maybe we could do numbering of MMC devices
> > in some type of a pre-probe routine? Is that what you're suggesting?
>
> Yes.
>
> So
On Mon, Nov 30, 2020 at 5:03 AM Peter Zijlstra wrote:
>
> > But but but...
> >
> > do_idle() # IRQs on
> > local_irq_disable(); # IRQs off
> > defaul_idle_call()# IRQs off
> lockdep_hardirqs_on(); # IRQs off, but lockdep things they're on
> >
> On Dec 1, 2020, at 00:19, Srinivas Pandruvada
> wrote:
>
> On Mon, 2020-11-30 at 16:23 +0800, Kai-Heng Feng wrote:
>>> On Nov 30, 2020, at 15:57, Daniel Lezcano <
>>> daniel.lezc...@linaro.org> wrote:
>>>
>>>
>>> [Added Srinivas]
>>>
>>> On 28/11/2020 18:54, Kai-Heng Feng wrote:
We
Jerry Snitselaar @ 2020-11-30 10:50 MST:
> Lu Baolu @ 2020-11-26 19:12 MST:
>
>> Hi Jerry,
>>
>> On 11/27/20 5:35 AM, Jerry Snitselaar wrote:
>>> Lu Baolu @ 2020-11-26 04:01 MST:
>>>
Hi Jerry,
On 2020/11/26 4:27, Jerry Snitselaar wrote:
> Is there a reason we check the
On Mon, Nov 30, 2020 at 6:28 AM Daniel Vetter wrote:
>
> So I guess kvm platforms that don't set KVM_ARCH_WANT_MMU_NOTIFIER exist,
> and at least on powerpc they're consistent with KVM_CAP_SYNC_MMU
> signalling that the guest pagetables stays in sync automatically with any
> updates. So for that
I spent some time looking into this:
I think there are actually two bugs here. The write-after-free in
kernfs_path_from_node_locked has an entirely different call trace
(towards the end of this log:
https://syzkaller.appspot.com/text?tag=CrashLog=16b1e0e950)
compared to the NULL pointer
On Mon, 2020-11-30 at 17:15 +, Joao Martins wrote:
> On 11/30/20 4:48 PM, David Woodhouse wrote:
> > On Mon, 2020-11-30 at 15:08 +, Joao Martins wrote:
> > > On 11/30/20 12:55 PM, David Woodhouse wrote:
> > > > On Mon, 2020-11-30 at 12:17 +, Joao Martins wrote:
> > > > > On 11/30/20
On Mon, 2020-11-30 at 23:02 +0530, Dwaipayan Ray wrote:
> Sorry I think i explained wrong. For words like "doesn't", it still
> has the same problem.
I think you explained it wrong when you didn't mention this is
_only_ a problem when using --codespell.
Likely it'd be better to use
On Fri, Nov 27, 2020 at 06:24:11PM +1100, Stephen Rothwell wrote:
> Caused by commit
>
> 6f4a038b9967 ("ASoC/SoundWire: rt715-sdca: First version of rt715 sdw sdca
> codec driver")
>
> I have reverted that commit for today.
I'll drop this, hopefully it can be re-added in future.
On Sun, Nov 29, 2020 at 1:20 PM Topi Miettinen wrote:
>
> Writing a new value of 3 to /proc/sys/kernel/randomize_va_space
> enables full randomization of memory mappings created with mmap(NULL,
> ...). With 2, the base of the VMA used for such mappings is random,
> but the mappings are created in
On Mon, Nov 30, 2020 at 01:31:23PM +, Daniel Scally wrote:
> To ensure we handle situations in which multiple sensors of the same
> model (and therefore _HID) are present in a system, we need to be able
> to iterate over devices matching a known _HID but unknown _UID and _HRV
> - add
On Tue, Dec 01, 2020 at 01:48:30AM +0800, Rongwei Wang wrote:
> MSR ARM driver aims to provide interfacs for user to read or write data to all
> system registers. Its functions is same as MSR driver (x86 platform). It
> mainly
> depends on kprobe and undef exception to read or write system
On Sun, Nov 29, 2020 at 11:57 PM Peter Zijlstra wrote:
>
> The idea was to flip all of arch_cpu_idle() to not enable interrupts.
I don't think that's realistic.
> This is suboptimal for things like x86 where arch_cpu_idle() is
> basically STI;HLT, but x86 isn't likely to actually use this code
On Mon, Nov 30, 2020 at 01:31:22PM +, Daniel Scally wrote:
> Where the fwnode graph is comprised of software_nodes, these will be
> assigned as the secondary to dev->fwnode. Check the v4l2_subdev's fwnode
> for a secondary and attempt to match against it during match_fwnode() to
> accommodate
On 11/30/2020 9:39 AM, Scott Branden wrote:
>
>
> On 2020-11-30 4:19 a.m., Lorenzo Pieralisi wrote:
>> On Thu, Oct 01, 2020 at 11:30:51AM +0530, Srinath Mannam wrote:
>>> This patch series contains fixes and improvements to pcie iproc driver.
>>>
>>> This patch set is based on Linux-5.9.0-rc2.
On 30/11/20 18:41, Sean Christopherson wrote:
pmd1 and pmd2 point to the same pte table, so:
ptr1 and ptr3 points to the same page.
ptr2 and ptr4 points to the same page.
The guess read-accesses to ptr1 first. So the hypervisor gets the
shadow pte page table with role.access=u-- among other
Dear RT folks!
I'm pleased to announce the v5.10-rc6-rt13 patch set.
Changes since v5.10-rc6-rt12:
- John's printk series was updated to his current status.
- The notifier lock has been made a raw_spinlock_t to avoid a
acquiring a sleeping lock in atomic context. Patch by Valentin
On 30/11/20 18:38, Sasha Levin wrote:
I am not aware of any public CI being done _at all_ done on
vhost-scsi, by CKI or everyone else. So autoselection should be done
only on subsystems that have very high coverage in CI.
Where can I find a testsuite for virtio/vhost? I see one for KVM, but
On Mon, Nov 30, 2020 at 07:28:57PM +0200, Laurent Pinchart wrote:
> On Mon, Nov 30, 2020 at 07:29:00PM +0200, Andy Shevchenko wrote:
> > On Mon, Nov 30, 2020 at 01:31:13PM +, Daniel Scally wrote:
...
> > > + if (!best_ep && fwnode && !IS_ERR_OR_NULL(fwnode->secondary))
> > > + return
On Mon, 30 Nov 2020, Ard Biesheuvel wrote:
> On Mon, 30 Nov 2020 at 16:51, Nicolas Pitre wrote:
>
> > Here's my version of the fix which should be correct. Warning: this
> > is completely untested, but should in theory produce the same code on
> > modern gcc.
> >
> > diff --git
Looks good,
Reviewed-by: Christoph Hellwig
membarrier() carefully propagates SYNC_CORE and RSEQ actions to all
other CPUs, but there are two issues.
- membarrier() does not sync_core() or rseq_preempt() the calling
CPU. Aside from the logic being mind-bending, this also means
that it may not be safe to modify user code through an
It seems to be that most RSEQ membarrier users will expect any
stores done before the membarrier() syscall to be visible to the
target task(s). While this is extremely likely to be true in
practice, nothing actually guarantees it by a strict reading of the
x86 manuals. Rather than providing this
Lu Baolu @ 2020-11-26 19:12 MST:
> Hi Jerry,
>
> On 11/27/20 5:35 AM, Jerry Snitselaar wrote:
>> Lu Baolu @ 2020-11-26 04:01 MST:
>>
>>> Hi Jerry,
>>>
>>> On 2020/11/26 4:27, Jerry Snitselaar wrote:
Is there a reason we check the requested guest address width against
the
iommu's
Hi all-
x86's sync_core_before_usermode() was bogus. Without the other
patches applied, it would never be called in a problematic context,
but that's about to change. In any event, sync_core_before_usermode()
should be correct.
The second patch fixes a minor issue, but it also makes the third
Hi,
Here is a config changes for TI K3 SoCs. This is needed for booting
the J721E board from an SD card.
I do have a follow up cleanup patch[1] once drivers/soc/ti merges are in,
which I think I will need to request later on.
[1]
sync_core_before_usermode() had an incorrect optimization. If we're
in an IRQ, we can get to usermode without IRET -- we just have to
schedule to a different task in the same mm and do SYSRET.
Fortunately, there were no callers of sync_core_before_usermode()
that could have had in_irq() or
In order to use the MSR-ARM driver in module and built-in ways, we need export
following symbols.
The MSR-ARM driver depends on function aarch64_insn_patch_text to modify the
text at runtime, and function aarch64_insn_read to read one instruction in the
specified address.
In addition, we need
On 11/25/20 9:32 PM, Huang Ying wrote:
> --- a/man2/set_mempolicy.2
> +++ b/man2/set_mempolicy.2
> @@ -113,6 +113,11 @@ A nonempty
> .I nodemask
> specifies node IDs that are relative to the set of
> node IDs allowed by the process's current cpuset.
> +.TP
> +.BR MPOL_F_NUMA_BALANCING " (since
Hi
MSR ARM driver aims to provide interfacs for user to read or write data to all
system registers. Its functions is same as MSR driver (x86 platform). It mainly
depends on kprobe and undef exception to read or write system registers
dynamicly.
In addition, this module create interfaces for each
By default, MSR-ARM is compiled as a module.
Signed-off-by: Rongwei Wang
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 5cfe3cf..952cf6a 100644
--- a/arch/arm64/configs/defconfig
+++
The function of MSR-ARM driver is similar to that of MSR module under
x86. It is used to read and write system registers in user mode, which is easy
to debug.
In the implementation of MSR-ARM module, because the current aarch64
architecture lacks the support of rdmsr and wrmsr instructions, we
On Mon, Nov 30, 2020 at 06:17:16PM +0200, Laurent Pinchart wrote:
> Hi Daniel,
>
> Thank you for the patch.
>
> The subject line is very long. We try to keep it within a 72 characters
> limit in the kernel. That can be a challenge sometimes, and expections
> can be accepted, but this one is
On Mon, 30 Nov 2020 17:07:09 +, Vincenzo Frascino wrote:
> UL in the definition of SYS_TFSR_EL1_TF1 was misspelled causing
> compilation issues when trying to implement in kernel MTE async
> mode.
>
> Fix the macro correcting the typo.
>
> Note: MTE async mode will be introduced with a
On Mon, Nov 30, 2020 at 01:31:16PM +, Daniel Scally wrote:
> Software nodes that are children of another software node should be
> unregistered before their parent. To allow easy unregistering of an array
> of software_nodes ordered parent to child, reverse the order in which
> this function
On 11/10/20 8:21 AM, Yu-cheng Yu wrote:
> Control-flow Enforcement Technology (CET) adds five MSRs. Introduce
> them and their XSAVES supervisor states:
>
> MSR_IA32_U_CET (user-mode CET settings),
> MSR_IA32_PL3_SSP (user-mode Shadow Stack pointer),
> MSR_IA32_PL0_SSP (kernel-mode
rch/ia64/configs/generic_defconfig |2 --
1 file changed, 2 deletions(-)
--- linux-next-20201130.orig/arch/ia64/configs/generic_defconfig
+++ linux-next-20201130/arch/ia64/configs/generic_defconfig
@@ -55,8 +55,6 @@ CONFIG_CHR_DEV_SG=m
CONFIG_SCSI_FC_ATTRS=y
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_QLOGIC_12
On Mon, Nov 30, 2020 at 9:04 AM Doug Anderson wrote:
>
> Without static assignment, maybe we could do numbering of MMC devices
> in some type of a pre-probe routine? Is that what you're suggesting?
Yes.
So basically, the way the async probing works for say SCSI is that we
have multiple "layers
Hi,
Please pull the following for TI K3 dts changes for v5.11 window.
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
On 11/29/20 5:26 AM, Matthew Wilcox wrote:
> On Sun, Nov 29, 2020 at 07:34:29PM +0800, Hillf Danton wrote:
>>> radix_tree_next_slot include/linux/radix-tree.h:422 [inline]
>>> idr_for_each+0x206/0x220 lib/idr.c:202
>>> io_destroy_buffers fs/io_uring.c:8275 [inline]
>>
>> Matthew, can you shed
Commit
fd8d9db3559a ("x86/resctrl: Remove superfluous kernfs_get() calls to prevent
refcount leak")
removed superfluous kernfs_get() calls in rdtgroup_ctrl_remove() and
rdtgroup_rmdir_ctrl(). That change resulted in an unused function
parameter to these two functions.
Clean up the unused
On Thu, 19 Nov 2020 10:27:09 +0800
Wei Li wrote:
> The feature lists don't match reality as of v5.10-rc4, update them
> accordingly (by features-refresh.sh).
>
> Fixes: aa65ff6b18e0 ("powerpc/64s: Implement queued spinlocks and rwlocks")
> Fixes: e95a4f8cb985 ("csky: Add SECCOMP_FILTER
Em Mon, Nov 30, 2020 at 05:30:12PM +, John Garry escreveu:
> On 27/11/2020 15:39, Alexandre Truong wrote:
> > Previously, this command returns no help message on aarch64:
> >
> >-> ./perf record --user-regs=?
> >
> >available registers:
> >Usage: perf record [] []
> >or:
On Sat, Nov 28, 2020, Lai Jiangshan wrote:
> On Sat, Nov 28, 2020 at 12:48 AM Paolo Bonzini wrote:
> >
> > On 26/11/20 01:05, Sean Christopherson wrote:
> > > On Fri, Nov 20, 2020, Lai Jiangshan wrote:
> > >> From: Lai Jiangshan
> > >>
> > >> Commit 41074d07c78b ("KVM: MMU: Fix inherited
As a performance enhancement, make the completion queue interrupts managed.
In addition, in commit bf0beec0607d ("blk-mq: drain I/O when all CPUs in a
hctx are offline"), CPU hotplug for MQ devices using managed interrupts
is made safe. So expose HW queues to blk-mq to take advantage of this.
Drivers for multi-queue platform devices may also want managed interrupts
for handling HW queue completion interrupts, so add support.
The function accepts an affinity descriptor pointer, which covers all IRQs
expected for the device.
The function is devm class as the only current in-tree user
The functionality of acpi_dev_irqresource_disabled() is same as in common
irqresource_disabled(), so drop acpi_dev_irqresource_disabled() in favour
of that function.
Signed-off-by: John Garry
---
drivers/acpi/resource.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
So far, managed interrupts are only used for PCI MSIs. This series adds
platform device support for managed interrupts. Initially this topic was
discussed at [0].
The method to enable managed interrupts is to allocate a group of IRQs for
the device, and then switch the interrupts to managed -
On Mon, Nov 30, 2020 at 11:21:20AM +0100, Borislav Petkov wrote:
> On Mon, Nov 30, 2020 at 03:03:36PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the tip tree got a conflict in:
> >
> > arch/x86/pci/i386.c
> >
> > between commit:
> >
> > ace091d17272
Add a function to allow the affinity of an interrupt be switched to
managed, such that interrupts allocated for platform devices may be
managed.
Suggested-by: Thomas Gleixner
Signed-off-by: John Garry
---
include/linux/interrupt.h | 8 +
kernel/irq/manage.c | 63
Add a common function to set the fields for a irq resource to disabled,
which mimics what is done in acpi_dev_irqresource_disabled(), with a view
to replace that function.
Signed-off-by: John Garry
---
include/linux/ioport.h | 7 +++
1 file changed, 7 insertions(+)
diff --git
My Donation To You in good faith.
May the peace of the Almighty God be with you and your Family,
With Due Respect and Humility, I was compelled to write you under
humanitarian ground. My name is Mrs Elena Adams, the Wife of Engineer
Ralph Alphonso Adams from United State Of America. I have took
On 2020-11-30 4:19 a.m., Lorenzo Pieralisi wrote:
> On Thu, Oct 01, 2020 at 11:30:51AM +0530, Srinath Mannam wrote:
>> This patch series contains fixes and improvements to pcie iproc driver.
>>
>> This patch set is based on Linux-5.9.0-rc2.
>>
>> Changes from v2:
>> - Addressed Bjorn's review
On Mon, Nov 30, 2020 at 09:00:27PM +0900, Bongsu jeon wrote:
> From: Bongsu Jeon
>
> Since S3FWRN82 NFC Chip, The UART interface can be used.
> S3FWRN82 supports I2C and UART interface.
>
> Signed-off-by: Bongsu Jeon
> ---
>
> Changes in v2:
> -change the compatible name.
> -change the
[Re: [PATCH 0/3] clear_warn_once: add timed interval resetting] On 29/11/2020
(Sun 19:08) Andi Kleen wrote:
> On Thu, Nov 26, 2020 at 01:30:26AM -0500, Paul Gortmaker wrote:
> > But you currently can't make use of clear_warn_once unless you've got
> > debugfs enabled and mounted - which may not
On Mon, Nov 30, 2020 at 09:33:46AM +0100, Paolo Bonzini wrote:
On 29/11/20 22:06, Sasha Levin wrote:
Plus all the testing we have for the stable trees, yes. It goes beyond
just compiling at this point.
Your very own co-workers (https://cki-project.org/) are pushing hard on
this effort around
On Mon, 23 Nov 2020 18:38:14 -0800
Bailu Lin wrote:
> This is a Chinese translated version of
> Documentation/arm64/elf_hwcaps.rst
>
> Signed-off-by: Bailu Lin
> ---
> Changes in v2:
> - Modify five translation issues as Alex sugguested.
> ---
> Documentation/arm64/elf_hwcaps.rst
On Sun, 29 Nov 2020 15:21:44 +0100, Lubomir Rintel wrote:
> Add binding document for the Dell Wyse 3020 a.k.a. "Ariel" Power Button.
>
> Signed-off-by: Lubomir Rintel
> Reviewed-by: Rob Herring
>
> ---
> Changes since v1:
> - Collect Rob's R-b
>
> .../bindings/input/ariel-pwrbutton.yaml
On Mon, 30 Nov 2020 21:00:27 +0900, Bongsu jeon wrote:
> From: Bongsu Jeon
>
> Since S3FWRN82 NFC Chip, The UART interface can be used.
> S3FWRN82 supports I2C and UART interface.
>
> Signed-off-by: Bongsu Jeon
> ---
>
> Changes in v2:
> -change the compatible name.
> -change the const to
From: Matteo Croce
Not all the reboot settings from both the kernel command line or sysfs
interface are available to all platforms.
Filter out reboot_type and reboot_force which are x86 only, and also
remove reboot_cpu on kernels without SMP support.
This saves some space, and avoid confusing
On Mon, Nov 30, 2020 at 07:35:30PM +0200, Andy Shevchenko wrote:
> On Mon, Nov 30, 2020 at 01:31:15PM +, Daniel Scally wrote:
...
> > for (i = 0; nodes[i].name; i++) {
> > + if (nodes[i].parent)
> > + if (!software_node_to_swnode(nodes[i].parent)) {
> > +
From: Matteo Croce
On some machines a quirk can force a specific reboot type.
Quirks are found during a DMI scan, the list of machines which need
special reboot handling is defined in reboot_dmi_table.
The kernel command line reboot= option overrides this via a global
variable `reboot_default`,
From: Matteo Croce
Some improvements to the sysfs reboot interface: hide not
working settings and support machines with known reboot quirks.
Matteo Croce (2):
reboot: allow to override reboot type if quirks are found
reboot: hide from sysfs not applicable settings
kernel/reboot.c | 58
On Monday 30 Nov 2020 at 17:05:31 (+), Qais Yousef wrote:
> I create 3 cpusets: 64bit, 32bit and mix. As the name indicates, 64bit
> contains
> all 64bit-only cpus, 32bit contains 32bit-capable ones and mix has a mixture
> of
> both.
>
> If I try to move my test binary to 64bit cpuset, it
On Fri, 27 Nov 2020 16:35:12 +0800, gao.yunxi...@gmail.com wrote:
> From: "jeson.gao"
>
> virtual thermal node definition description in dts file
>
> Signed-off-by: jeson.gao
> ---
> .../thermal/sprd-virtual-thermal.yaml | 38 +++
> 1 file changed, 38 insertions(+)
>
On Sun, 29 Nov 2020 08:51:21 +1300
Barry Song wrote:
> early_param memmap is only implemented on X86, MIPS and XTENSA. To avoid
> wasting users’ time on trying this on platform like ARM, mark it clearly.
>
> Signed-off-by: Barry Song
> Reviewed-by: Mike Rapoport
> ---
> -v2:
> * add
On Mon, Nov 30, 2020 at 01:31:15PM +, Daniel Scally wrote:
> Registering software_nodes with the .parent member set to point to a
> currently unregistered software_node has the potential for problems,
> so enforce parent -> child ordering in arrays passed to this function.
I agree with
From: Stephane Eranian
Extend sample-parsing test cases to support new sample type
PERF_SAMPLE_CODE_PAGE_SIZE.
Acked-by: Namhyung Kim
Signed-off-by: Stephane Eranian
---
tools/perf/tests/sample-parsing.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
On Mon, Nov 30, 2020 at 03:00:13PM +0100, Paolo Bonzini wrote:
On 30/11/20 14:57, Greg KH wrote:
Every patch should be "fixing a real issue"---even a new feature. But the
larger the patch, the more the submitters and maintainers should be trusted
rather than a bot. The line between feature
From: Stephane Eranian
Add a new sort dimension "code_page_size" for common sort.
With this option applied, perf can sort and report by sample's code page
size.
For example,
perf report --stdio --sort=comm,symbol,code_page_size
# To display the perf.data header info, please use
#
On Fri, 27 Nov 2020 11:28:55 +0800, Gene Chen wrote:
> From: Gene Chen
>
> Add bindings document for LED support on MT6360 PMIC
>
> Signed-off-by: Gene Chen
> ---
> .../devicetree/bindings/leds/leds-mt6360.yaml | 164
> +
> 1 file changed, 164 insertions(+)
> create
From: Stephane Eranian
Display sampled code page sizes when PERF_SAMPLE_CODE_PAGE_SIZE was set.
For example,
perf script --fields comm,event,ip,code_page_size
dtlb mem-loads:uP:445777 4K
dtlb mem-loads:uP:40f724 4K
dtlb mem-loads:uP:
From: Stephane Eranian
Adds the infrastructure to sample the code address page size.
Introduce a new --code-page-size option for perf record.
Acked-by: Namhyung Kim
Signed-off-by: Stephane Eranian
---
tools/perf/Documentation/perf-record.txt | 3 +++
tools/perf/builtin-record.c
On Thu, Nov 26, 2020 at 02:06:28PM -0700, Mathieu Poirier wrote:
> This patch adds a binding to guide the remoteproc core on how to deal with
> remote processors in two cases:
>
> 1) When an application holding a reference to a remote processor character
>device interface crashes.
>
> 2)
On Mon, Nov 30, 2020 at 09:05:48AM -0700, Rob Herring wrote:
> On Sun, Nov 22, 2020 at 11:45 PM Jianjun Wang
> wrote:
> > On Thu, 2020-11-19 at 14:28 -0600, Bjorn Helgaas wrote:
> > > "Add new generation" really contains no information. And "mediatek"
> > > is already used for the
From: Kan Liang
Display the data page size if it is available.
Can be configured by the user, for example:
perf script --fields comm,event,phys_addr,data_page_size
dtlb mem-loads:uP:3fec82ea8 4K
dtlb mem-loads:uP:3fec82e90 4K
dtlb
801 - 900 of 1677 matches
Mail list logo
