On Tue, 23 Feb 2021 15:57:40 +0100
Gerald Schaefer wrote:
[...]
> What I do not understand is how __free_huge_page() would be called at all
> in the call trace below (set_max_huge_pages -> alloc_pool_huge_page ->
> __free_huge_page -> hugepage_subpool_put_pages). From the code it seems
> that
On 2/22/21 11:19 PM, Andrii Nakryiko wrote:
+ bpf_task_storage_lock();
sdata = bpf_local_storage_update(
task, (struct bpf_local_storage_map *)map, value, map_flags);
this should probably be container_of() instead of casting
bpf_task_storage.c uses casting in
GE CS1000 has some more custom USB IDs for CP2102N; add them
to the driver to have working auto-probing.
Signed-off-by: Sebastian Reichel
---
drivers/usb/serial/cp210x.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
index
On Tue, Feb 23, 2021 at 07:33:46AM -0800, Andy Lutomirski wrote:
>
> > On Feb 23, 2021, at 4:44 AM, Aili Yao wrote:
> >
> > On Fri, 5 Feb 2021 17:01:35 +0800
> > Aili Yao wrote:
> >
> >> When one page is already hwpoisoned by MCE AO action, processes may not
> >> be killed, processes mapping
On Mon, 22 Feb 2021 at 15:48, Sami Tolvanen wrote:
>
> Hi,
>
> On Sun, Feb 21, 2021 at 11:18 PM Jindong Yue wrote:
> >
> > There are four different callback functions that are used for the
> > rproc_handle_resource_t callback that all have different second
> > parameter types.
> >
> >
On Mon, Feb 22, 2021 at 9:55 PM Shakeel Butt wrote:
[snip]
> --- a/include/linux/memcontrol.h
> +++ b/include/linux/memcontrol.h
> @@ -596,6 +596,9 @@ static inline bool mem_cgroup_below_min(struct mem_cgroup
> *memcg)
> }
>
> int mem_cgroup_charge(struct page *page, struct mm_struct *mm,
On Tue, Feb 23, 2021, Like Xu wrote:
> When the processor that support model-specific LBR generates a debug
> breakpoint event, it automatically clears the LBR flag. This action
> does not clear previously stored LBR stack MSRs. (Intel SDM 17.4.2)
>
> Signed-off-by: Like Xu
> ---
>
On 2/18/21 3:05 PM, Jonathan Cameron wrote:
On Wed, 17 Feb 2021 10:34:38 +0200
Alexandru Ardelean wrote:
From: Mircea Caprioru
A PWM signal will be used as a trigger source to have a deterministic
sampling frequency since this family of DAC has no hardware interrupt
source.
This feature is
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 3b9cdafb5358eb9f3790de2f728f765fef100731
commit: 344bb20b159dd0996e521c0d4c131a6ae10c322a powerpc/syscall: Make
interrupt.c buildable on PPC32
date: 12 days ago
config: powerpc64-randconfig-r013-20210223
From: Alexandru Tachici
Currently AD7124-8 driver cannot use more than 8 IIO channels
because it was assigning the channel configurations bijectively
to channels specified in the device-tree. This is not possible
to do when using more than 8 channels as AD7124-8 has only 8
configuration
On 2/23/2021 8:01 AM, Álvaro Fernández Rojas wrote:
> Some devices may need to perform a reset before using the RNG, such as the
> BCM6368.
>
> Signed-off-by: Álvaro Fernández Rojas
Since the reset is unique to the 6368, you may want to make the property
mandatory for the 6368 compatible
From: Alexandru Tachici
Currently AD7124-8 driver cannot use more than 8 IIO channels
because it was assigning the channel configurations bijectively
to channels specified in the device-tree. This is not possible
to do when using more than 8 channels as AD7124-8 has only 8
configuration
On Tue, 23 Feb 2021 15:57:57 +
Andrew Scull wrote:
> There is some non-trivial config-based logic to get the file name and
> line number associated with a bug. Factor this out to a getter that can
> be resused.
>
> Signed-off-by: Andrew Scull
> Cc: Peter Zijlstra
> Cc: "Steven Rostedt
On Tue, 23 Feb 2021 10:28:46 +0800 Jiapeng Chong wrote:
> Fix the following coccicheck warnings:
>
> ./drivers/net/netdevsim/fib.c:564:2-3: Unneeded semicolon.
>
> Reported-by: Abaci Robot
> Signed-off-by: Jiapeng Chong
# Form letter - net-next is closed
We have already sent the networking
On 2/19/21 2:27 AM, Stephen Boyd wrote:
Quoting gabriel.fernan...@foss.st.com (2021-02-12 00:08:40)
On 2/9/21 9:00 AM, Stephen Boyd wrote:
Quoting gabriel.fernan...@foss.st.com (2021-01-26 01:01:08)
From: Gabriel Fernandez
'ck_rtc' has multiple clocks as input (ck_hsi, ck_lsi, and
Hello,
Md Sadre Alam wrote on Tue, 23 Feb 2021
01:34:27 +0530:
> From QPIC version 2.0 onwards new register got added to read last
a new
> codeword. This change will add the READ_LOCATION_LAST_CW_n register.
Add support for this
Good morning,
I have received your patchset but currently don't see having the time
to look at it before the middle of March.
Thanks,
Mathieu
On Tue, 23 Feb 2021 at 08:44, Ben Levinsky wrote:
>
> R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this
> remotproc driver, we can boot
- /*
-* Ask OP-TEE to free all cached shared memory objects to decrease
-* reference counters and also avoid wild pointers in secure world
-* into the old shared memory range.
-*/
- optee_disable_shm_cache(optee);
+ if (shutdown) {
+
On Tue, 23 Feb 2021 15:57:56 +
Andrew Scull wrote:
> report_bug() will return early if it cannot find a bug corresponding to
> the provided address. The subsequent test for the bug will always be
> true so remove it.
Fixes: 1b4cfe3c0a30d ("lib/bug.c: exclude non-BUG/WARN exceptions from
Alex Riesen, Tue, Feb 23, 2021 16:51:26 +0100:
> Ilia Mirkin, Tue, Feb 23, 2021 16:46:52 +0100:
> > I'd recommend using xf86-video-nouveau in any case, but some distros
>
> I would like try this out. Do you know how to force the xorg server to
> choose this driver instead of modesetting?
Found
Hello,
Md Sadre Alam wrote on Mon, 22 Feb 2021
20:35:43 +0530:
> This change will add helper nandc_set_read_loc() to configure
> location register value. QPIC V2 on wards there is separate
> location register to read the last code word. This helper
> will use to configure location register for
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
Signed-off-by: Álvaro Fernández Rojas
---
v2: change flag name and improve documentation as suggested by Alan Stern.
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
Signed-off-by: Álvaro Fernández Rojas
---
v2: change flag name and improve documentation as suggested by Alan Stern.
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
Álvaro Fernández Rojas (2):
dt-bindings: usb: generic-ehci: document ignore-oc flag
usb: host: ehci-platform: add ignore_oc DT
* Piotr Figiel:
> diff --git a/include/uapi/linux/ptrace.h b/include/uapi/linux/ptrace.h
> index 83ee45fa634b..d54cf6b6ce7c 100644
> --- a/include/uapi/linux/ptrace.h
> +++ b/include/uapi/linux/ptrace.h
> @@ -102,6 +102,14 @@ struct ptrace_syscall_info {
> };
> };
>
> +#define
Hello,
Md Sadre Alam wrote on Mon, 22 Feb 2021
13:05:42 +0530:
> This change will rename parameter name in macro
> nandc_set_read_loc().renamed parameter names are
> cw_offset, read_size, is_last_read_loc.
> Sinc in QPIC V2 on-wards there is separate location
> register to read last code word,
Hello.
On Mon, Feb 22, 2021 at 04:12:12PM +0100, Romain Perier
wrote:
> --- a/kernel/cgroup/cgroup.c
> +++ b/kernel/cgroup/cgroup.c
> @@ -2265,7 +2265,7 @@ int task_cgroup_path(struct task_struct *task, char
> *buf, size_t buflen)
Actually, this function isn't used at all. So I'd instead
> What I think is qemu has not an easy to get the MCE signature from host or
> currently no methods for this
> So qemu treat all AR will be No RIPV, Do more is better than do less.
RIPV would be important in the guest in the case where the guest can fix the
problem that caused
the machine check
Hello,
Md Sadre Alam wrote on Mon, 22 Feb 2021
11:54:55 +0530:
> This change will add helper qcom_nandc_is_last_cw()
Use the imperative form, something like:
"
Add the qcom_nandc_is_last_cw() helper which checks if the input cw
index is the last one or not.
"
> which will check for last code
On Tue, Feb 23, 2021 at 04:04:16PM +0100, Heiko Thiery wrote:
> It is not only the PHC clock that stops. Rather, it is the entire
> ethernet building block in the SOC that is disabled, including the
> PHC.
Sure, but why does the driver do that?
Thanks,
Richard
On Tue, Feb 23, 2021 at 05:04:57PM +0100, Álvaro Fernández Rojas wrote:
> Hi Alan,
>
> > El 23 feb 2021, a las 16:54, Alan Stern
> > escribió:
> >
> > On Tue, Feb 23, 2021 at 04:50:04PM +0100, Álvaro Fernández Rojas wrote:
> >> Over-current reporting isn't supported on some platforms such as
Hello,
Md Sadre Alam wrote on Mon, 22 Feb 2021
01:55:01 +0530:
> This change will convert nandc to chip in Read/Write helper, this
> change is needed because if we wnated to access number of steps
> in Read/Write helper then we need to get the chip->ecc.steps,
> currentlly its not
Hi,
On Tue, Feb 23, 2021 at 4:01 AM Sumit Garg wrote:
>
> @@ -103,7 +103,6 @@ extern int kdb_getword(unsigned long *, unsigned long,
> size_t);
> extern int kdb_putword(unsigned long, unsigned long, size_t);
>
> extern int kdbgetularg(const char *, unsigned long *);
> -extern int
Hi Alan,
> El 23 feb 2021, a las 16:54, Alan Stern escribió:
>
> On Tue, Feb 23, 2021 at 04:50:04PM +0100, Álvaro Fernández Rojas wrote:
>> Over-current reporting isn't supported on some platforms such as bcm63xx.
>> These devices will incorrectly report over-current if this flag isn't
>>
On 2/23/21 3:09 AM, Yang Li wrote:
fixed the following coccicheck:
./drivers/net/ipa/ipa_smp2p.c:186:7-27: ERROR: Threaded IRQ with no
primary handler requested without IRQF_ONESHOT
Make sure threaded IRQs without a primary handler are always request
with IRQF_ONESHOT
SMP2P interrupts are
On 2/23/21 7:29 AM, dai@oracle.com wrote:
On 2/23/21 2:32 AM, Luis Henriques wrote:
On Mon, Feb 22, 2021 at 08:25:27AM -0800, dai@oracle.com wrote:
On 2/22/21 2:24 AM, Luis Henriques wrote:
A regression has been reported by Nicolas Boichat, found while
using the
copy_file_range
hrtimer_force_reprogram() and hrtimer_interrupt() invokes
__hrtimer_get_next_event() to find the earliest expiry time of hrtimer
bases. __hrtimer_get_next_event() does not update
cpu_base::[softirq_]_expires_next to preserve reprogramming logic. That
needs to be done at the callsites.
This was already fixed by a patch from Yang Li .
Alex
On Tue, Feb 23, 2021 at 1:13 AM Jiapeng Chong
wrote:
>
> Fix the following coccicheck warnings:
>
> ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c:8260:16-21: WARNING:
> conversion to bool not needed here.
>
> Reported-by: Abaci Robot
Some devices may need to perform a reset before using the RNG, such as the
BCM6368.
Álvaro Fernández Rojas (2):
dt-bindings: rng: bcm2835: document reset support
hwrng: bcm2835: add reset support
.../devicetree/bindings/rng/brcm,bcm2835.yaml | 5 +
Some devices may need to perform a reset before using the RNG, such as the
BCM6368.
Signed-off-by: Álvaro Fernández Rojas
---
v2: document reset support.
Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml | 5 +
1 file changed, 5 insertions(+)
diff --git
BCM6368 devices need to reset the in order to generate true random numbers.
This is what BCM6368 produces without a reset:
root@OpenWrt:/# cat /dev/hwrng | rngtest -c 1000
rngtest 6.10
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions.
report_bug() will return early if it cannot find a bug corresponding to
the provided address. The subsequent test for the bug will always be
true so remove it.
Signed-off-by: Andrew Scull
Cc: Peter Zijlstra
Cc: "Steven Rostedt (VMware)"
---
lib/bug.c | 33 +++--
1
To aid with debugging, add details of the source of a panic. This is
done by having nVHE hyp exit to nvhe_hyp_panic_handler() rather than
directly to panic(). The handler will then add the extra details for
debugging before panicking the kernel.
If the panic was due to a BUG(), look up the
hyp_panic() reports the address of the panic by using ELR_EL2, but this
isn't a useful address when hyp_panic() is called directly. Replace such
direct calls with BUG() and BUG_ON() which use BRK to trigger and
exception that then goes to hyp_panic() with the correct address. Also
remove the
There is some non-trivial config-based logic to get the file name and
line number associated with a bug. Factor this out to a getter that can
be resused.
Signed-off-by: Andrew Scull
Cc: Peter Zijlstra
Cc: "Steven Rostedt (VMware)"
---
include/linux/bug.h | 3 +++
lib/bug.c | 27
Panics from arm64's nVHE hyp mode are hard to interpret. This series
adds some more debug info to help with diagnosis.
Using BUG() in nVHE hyp gives a meaningful address to locate invariants
that fail to hold. The host can also look up the bug to provide the file
and line, if the debug configs
Hi Yanan,
I wanted to review the patches, but unfortunately I get an error when trying to
apply the first patch in the series:
Applying: KVM: arm64: Move the clean of dcache to the map handler
error: patch failed: arch/arm64/kvm/hyp/pgtable.c:464
error: arch/arm64/kvm/hyp/pgtable.c: patch does
On Tue, Feb 23, 2021 at 04:50:04PM +0100, Álvaro Fernández Rojas wrote:
> Over-current reporting isn't supported on some platforms such as bcm63xx.
> These devices will incorrectly report over-current if this flag isn't properly
> activated.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
>
On Tue, Feb 23, 2021 at 09:50:35AM -0600, Daniel Díaz wrote:
> Hello!
>
> If I may add to the nit-picking...
>
> On Tue, 23 Feb 2021 at 09:23, Guenter Roeck wrote:
> > On 2/22/21 10:19 PM, Jason Wang wrote:
> > > We used to prompt CONFIG_VIRTIO_PCI_MODERN to user which may bring a
> > > lot of
On Mon 2021-02-22 16:58:46, Yiwei Zhang wrote:
> Since you awesome guys are here, I do have another kthread related
> question, and hopefully to get some suggestions:
>
> Below are the conditions:
> 1. The caller threads queuing the work are normal threads(non-RT).
> 2. The worker thread is a
Hi,
On 01/21, Enzo Matsumiya wrote:
Commit c2922f174fa0 ("scsi: smartpqi: fix LUN reset when fw bkgnd thread is
hung")
added support for a timeout on LUN resets.
However, when there are 2 or more devices connected to the same
controller and you hot-remove one of them, I/O will stall on the
Ilia Mirkin, Tue, Feb 23, 2021 16:46:52 +0100:
> On Tue, Feb 23, 2021 at 10:36 AM Alex Riesen
> wrote:
> > Ilia Mirkin, Tue, Feb 23, 2021 15:56:21 +0100:
> > > On Tue, Feb 23, 2021 at 9:26 AM Alex Riesen
> > > wrote:
> > > >
> > > > This change broke X cursor in my setup, and reverting the
Hi Micke,
On Fri, 12 Feb 2021, Beckius, Mikael wrote:
> Thanks for the update and sorry for the late reply. After long-term
> testing of the patch, storm detection improved, it turns out that a
> similar problem can occur if hrtimer_interrupt runs during
> clock_settime. In this case it seems
On 23/02/21 14:45, Vincent Guittot wrote:
> On Tue, 23 Feb 2021 at 13:03, Valentin Schneider
> wrote:
>>
>>
>> +Vincent
>>
>> On 22/02/21 09:12, syzbot wrote:
>> > syzbot has found a reproducer for the following issue on:
>> >
>> > HEAD commit:31caf8b2 Merge branch 'linus' of
>> >
Hello!
If I may add to the nit-picking...
On Tue, 23 Feb 2021 at 09:23, Guenter Roeck wrote:
> On 2/22/21 10:19 PM, Jason Wang wrote:
> > We used to prompt CONFIG_VIRTIO_PCI_MODERN to user which may bring a
> > lot of confusion. E.g it may break various default configs which want
> > virtio
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
Álvaro Fernández Rojas (2):
dt-bindings: usb: generic-ehci: document ignore-oc flag
usb: host: ehci-platform: add ignore-oc DT
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
Signed-off-by: Álvaro Fernández Rojas
---
drivers/usb/host/ehci-platform.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
Hi George,
On Tue, Feb 23, 2021 at 09:35:32AM -0500, George Kennedy wrote:
>
> On 2/23/2021 5:33 AM, Mike Rapoport wrote:
> > (re-added CC)
> >
> > On Mon, Feb 22, 2021 at 08:24:59PM -0500, George Kennedy wrote:
> > > On 2/22/2021 4:55 PM, Mike Rapoport wrote:
> > > > On Mon, Feb 22, 2021 at
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
Signed-off-by: Álvaro Fernández Rojas
---
Documentation/devicetree/bindings/usb/generic-ehci.yaml | 5 +
1 file changed, 5
On 2/10/21 6:46 PM, Kees Cook wrote:
> As started by commit 05a5f51ca566 ("Documentation: Replace lkml.org
> links with lore"), replace lkml.org links with lore to better use a
> single source that's more likely to stay available long-term.
>
> Signed-off-by: Kees Cook
Reviewed-by: Boris
On Sat, Feb 6, 2021 at 1:09 AM Matteo Croce wrote:
>
> From: Matteo Croce
>
> With this series a monotonically increasing number is added to disks,
> precisely in the genhd struct, and it's exported in sysfs and uevent.
>
> This helps the userspace correlate events for devices that reuse the
>
On Tue, Feb 23, 2021 at 10:36 AM Alex Riesen
wrote:
>
> Ilia Mirkin, Tue, Feb 23, 2021 15:56:21 +0100:
> > On Tue, Feb 23, 2021 at 9:26 AM Alex Riesen
> > wrote:
> > > Lyude Paul, Tue, Jan 19, 2021 02:54:13 +0100:
> > > > diff --git a/drivers/gpu/drm/nouveau/dispnv50/disp.c
> > > >
Hi,
> Can't you just use the asm-generic versions instead?
Hmm, yes, for fb.h and vga.h that should work, since they should never
be used. For vga.h it would be wrong since it assumes the VGA memory is
mapped into the CPU memory, but since it should never run it would still
address the
On 2/19/21 10:40 AM, Juergen Gross wrote:
> The first four patches are fixes for XSA-332. The avoid WARN splats
> and a performance issue with interdomain events.
>
> Patches 5 and 6 are some additions to event handling in order to add
> some per pv-device statistics to sysfs and the ability to
R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this
remoteproc driver, we can boot the R5 sub-system in two different
configurations -
* Split
* Lockstep
The Xilinx R5 Remoteproc Driver boots the R5's via calls to the Xilinx
Platform Management Unit that handles the
Add shutdown/wakeup a resource eemi operations to shutdown
or bringup a resource.
Note alignment of args matches convention of other fn's in this file.
The reason being that the long fn name results in aligned args that
otherwise go over 80 chars so shift right to avoid this
Signed-off-by: Ben
Add ZynqMP firmware ioctl enums for RPU configuration and TCM Nodes for
later use via request_node and release_node
Signed-off-by: Ben Levinsky
---
include/linux/firmware/xlnx-zynqmp.h | 23 +++
1 file changed, 23 insertions(+)
diff --git
R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this
remotproc driver, we can boot the R5 sub-system in two different
configurations -
* Split
* Lockstep
The Xilinx R5 Remoteproc Driver boots the R5's via calls to the Xilinx
Platform Management Unit that handles the R5
Add binding for ZynqMP R5 OpenAMP.
Represent the RPU domain resources in one device node. Each RPU
processor is a subnode of the top RPU domain node.
Signed-off-by: Jason Wu
Signed-off-by: Wendy Liang
Signed-off-by: Michal Simek
Signed-off-by: Ben Levinsky
---
This patch adds APIs to access to configure RPU and its
processor-specific memory.
That is query the run-time mode of RPU as either split or lockstep as well
as API to set this mode. In addition add APIs to access configuration of
the RPUs' tightly coupled memory (TCM).
Signed-off-by: Ben
Hi Johannes,
On Tue, Feb 23, 2021 at 4:27 PM Johannes Berg wrote:
> From: Johannes Berg
>
> Adjust the kconfig a little to allow disabling NO_IOMEM in UML. To
> make an "allyesconfig" with CONFIG_NO_IOMEM=n build, adjust a few
> Kconfig things elsewhere and add dummy asm/fb.h and asm/vga.h
Hi Linus,
Please pull below to receive modules updates for the v5.12 merge window.
A summary can be found in the signed tag.
Thank you,
Jessica
---
The following changes since commit 19c329f6808995b142b3966301f217c831e7cf31:
Linux 5.11-rc4 (2021-01-17 16:37:05 -0800)
are available in the
On Tue, Feb 23, 2021 at 11:50:05AM +0100, Oscar Salvador wrote:
> > CPU0: CPU1:
> > set_compound_page_dtor(HUGETLB_PAGE_DTOR);
> > memory_failure_hugetlb
> > get_hwpoison_page
> > __get_hwpoison_page
> > get_page_unless_zero
> >
On Thu, Feb 18, 2021 at 04:48:22PM -0800, Axel Rasmussen wrote:
> @@ -4645,8 +4646,18 @@ int hugetlb_mcopy_atomic_pte(struct mm_struct *dst_mm,
> spinlock_t *ptl;
> int ret;
> struct page *page;
> + int writable;
>
> - if (!*pagep) {
> + mapping =
Ilia Mirkin, Tue, Feb 23, 2021 15:56:21 +0100:
> On Tue, Feb 23, 2021 at 9:26 AM Alex Riesen
> wrote:
> > Lyude Paul, Tue, Jan 19, 2021 02:54:13 +0100:
> > > diff --git a/drivers/gpu/drm/nouveau/dispnv50/disp.c
> > > b/drivers/gpu/drm/nouveau/dispnv50/disp.c
> > > index
On Tue, Feb 23, 2021 at 05:24:23PM +0800, Muchun Song wrote:
> SLUB currently account kmalloc() and kmalloc_node() allocations larger
> than order-1 page per-node. But it forget to update the per-memcg
> vmstats. So it can lead to inaccurate statistics of "slab_unreclaimable"
> which is from
On Tue, Feb 23, 2021 at 05:11:01PM +0800, Muchun Song wrote:
> We use a global percpu int_active_memcg variable to store the remote
> memcg when we are in the interrupt context. But get_active_memcg always
> return the current->active_memcg or root_mem_cgroup. The remote memcg
> (set in the
> On Feb 23, 2021, at 3:29 AM, Peter Zijlstra wrote:
>
> On Mon, Feb 22, 2021 at 09:50:28PM -0800, Andy Lutomirski wrote:
>> On a 32-bit fast syscall that fails to read its arguments from user
>> memory, the kernel currently does syscall exit work but not
>> syscall exit work. This would
> On Feb 23, 2021, at 4:44 AM, Aili Yao wrote:
>
> On Fri, 5 Feb 2021 17:01:35 +0800
> Aili Yao wrote:
>
>> When one page is already hwpoisoned by MCE AO action, processes may not
>> be killed, processes mapping this page may make a syscall include this
>> page and result to trigger a
On 2/23/21 2:32 AM, Luis Henriques wrote:
On Mon, Feb 22, 2021 at 08:25:27AM -0800, dai@oracle.com wrote:
On 2/22/21 2:24 AM, Luis Henriques wrote:
A regression has been reported by Nicolas Boichat, found while using the
copy_file_range syscall to copy a tracefs file. Before commit
On Tue, Feb 23, 2021 at 12:31 PM Luis Henriques wrote:
>
> On Mon, Feb 22, 2021 at 08:25:27AM -0800, dai@oracle.com wrote:
> >
> > On 2/22/21 2:24 AM, Luis Henriques wrote:
> > > A regression has been reported by Nicolas Boichat, found while using the
> > > copy_file_range syscall to copy a
On Mon, 22 Feb 2021 09:43:51 +0800, Zhiyuan Dai wrote:
> This patch move the pointer location to fix coding style issues,
> improve code reading.
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/mm: Fixed some coding style issues
https://git.kernel.org/arm64/c/2e8acca1911b
Cheers,
On Tue, 23 Feb 2021 16:25:34 +0800, He Zhe wrote:
> As stated in linux/errno.h, ENOTSUPP should never be seen by user programs.
> When we set up uprobe with 32-bit perf and arm64 kernel, we would see the
> following vague error without useful hint.
>
> The sys_perf_event_open() syscall returned
From: Johannes Berg
To support testing of PCI/PCIe drivers in UML, add a PCI bus
support driver. This driver uses virtio, which in UML is really
just vhost-user, to talk to devices, and adds the devices to
the virtual PCI bus in the system.
Since virtio already allows DMA/bus mastering this
From: Johannes Berg
This function doesn't exist, remove its declaration.
Signed-off-by: Johannes Berg
---
arch/um/include/shared/kern_util.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/um/include/shared/kern_util.h
b/arch/um/include/shared/kern_util.h
index
From: Johannes Berg
The UM virtual PCI devices currently cannot be suspended properly
since the virtio driver already disables VQs well before the PCI
bus's suspend_noirq wants to complete the transition by writing to
PCI config space.
After trying around for a long time with moving the devices
From: Johannes Berg
Add IO memory emulation that uses callbacks for read/write to
the allocated regions. The callbacks can be registered by the
users using logic_iomem_alloc().
To use, an architecture must 'select LOGIC_IOMEM' in Kconfig
and then include into asm/io.h to get
the
From: Johannes Berg
We should be able to ndelay() from any context, even from an
interrupt context! However, this is broken (not functionally,
but locking-wise) in time-travel because we'll get into the
time-travel code and enable interrupts to handle messages on
other time-travel aware
From: Johannes Berg
If we happen to get multiple messages while IRQS are already
suspended, we still need to handle them, since otherwise the
simulation blocks.
Remove the "prevent nesting" part, time_travel_add_irq_event()
will deal with being called multiple times just fine.
Signed-off-by:
From: Johannes Berg
Adjust the kconfig a little to allow disabling NO_IOMEM in UML. To
make an "allyesconfig" with CONFIG_NO_IOMEM=n build, adjust a few
Kconfig things elsewhere and add dummy asm/fb.h and asm/vga.h files.
Signed-off-by: Johannes Berg
---
arch/um/Kconfig| 4
Hi,
In order to simulate some devices and write tests completely
independent of real PCI devices, we continued the development
of time-travel and related bits, and are adding PCI support
here now.
The way it works is that it communicates with the outside (of
UML) with virtio, which we previously
On 02/21/21 21:43, shuo.a@intel.com wrote:
> From: Shuo Liu
>
> Without cpu hotplug support, vCPU cannot be removed from a Service VM.
> Don't expose remove_cpu sysfs when CONFIG_HOTPLUG_CPU disabled.
>
> Signed-off-by: Shuo Liu
> Acked-by: Randy Dunlap # build-tested
> Cc: Stephen
Hey Hsin-Yi,
This patch looks good to me, feel free to add my r-b.
Reviewed-by: Robert Foss
On Fri, 15 Jan 2021 at 08:05, Hsin-Yi Wang wrote:
>
> When suspending the driver, anx7625_power_standby() will be called to
> turn off reset-gpios and enable-gpios. However, power supplies are not
>
On 2/22/21 10:19 PM, Jason Wang wrote:
> We used to prompt CONFIG_VIRTIO_PCI_MODERN to user which may bring a
> lot of confusion. E.g it may break various default configs which want
> virtio devices.
>
> So this patch fixes this by hiding the prompot and documenting the
> dependency. While at it,
On Tue, Feb 23, 2021 at 1:25 AM Muchun Song wrote:
>
> SLUB currently account kmalloc() and kmalloc_node() allocations larger
> than order-1 page per-node. But it forget to update the per-memcg
> vmstats. So it can lead to inaccurate statistics of "slab_unreclaimable"
> which is from memory.stat.
On Tue, Feb 23 2021 at 15:02, Thomas Gleixner wrote:
> Linus,
>
> please pull the latest objtool/core branch from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> objtool-core-2021-02-23
>
> up to: aafeb14e9da2: objtool: Support stack-swizzle
>
> objtool updates:
>
> - Make
On Thu, Feb 18, 2021 at 04:48:19PM -0800, Axel Rasmussen wrote:
[...]
> @@ -1290,14 +1299,20 @@ static int userfaultfd_register(struct
> userfaultfd_ctx *ctx,
> ret = -EINVAL;
> if (!uffdio_register.mode)
> goto out;
> - if (uffdio_register.mode &
The driver sets auto_runtime_pm to true, but it doesn't call
pm_runtime_enable(), which results in "Failed to power device" when PM support
is enabled.
Signed-off-by: Álvaro Fernández Rojas
---
drivers/spi/spi-bcm63xx.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
On 2/23/21 12:00 AM, Álvaro Fernández Rojas wrote:
> bcm7038_wdt can be used on bmips big endian (bcm63xx) devices too.
>
> Signed-off-by: Álvaro Fernández Rojas
With the assumption that the driver indeed does not need memory
barriers,
Reviewed-by: Guenter Roeck
Thanks,
Guenter
Both BCM63xx SPI drivers enable auto_runtime_pm, but they don't call
pm_runtime_enable(), which results in "Failed to power device" when PM support
is enabled.
Álvaro Fernández Rojas (2):
spi: bcm63xx-spi: fix pm_runtime
spi: bcm63xx-hsspi: fix pm_runtime
drivers/spi/spi-bcm63xx-hsspi.c | 7
601 - 700 of 1024 matches
Mail list logo
