collapse_file() in khugepaged passes PAGE_SIZE as the number of pages to be
read ahead to page_cache_sync_readahead(). It seems this was expressed as a
number of bytes rather than a number of pages.
Fix it to use the number of pages to the end of the window instead.
Fixes: 99cb0dbd47a1
Hi!
On Wed, Sep 02, 2020 at 06:46:45AM +, Christophe Leroy wrote:
> ld crashes:
>
> LD arch/powerpc/kernel/vdso32/vdso32.so.dbg
> /bin/sh: line 1: 23780 Segmentation fault (core dumped)
> ppc-linux-ld -EB -m elf32ppc -shared -soname linux-vdso32.so.1
> --eh-frame-hdr
The pcd driver does not have a ->revalidate_disk method, so it can just
use bdev_check_media_change without any additional changes.
Signed-off-by: Christoph Hellwig
---
drivers/md/md.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index
On Wed, Sep 02, 2020 at 07:33:12AM -0500, Bjorn Helgaas wrote:
> On Wed, Sep 02, 2020 at 11:07:43AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the pci tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> >
> > drivers/pci/pci-driver.c: In
Just merge the trivial function into its only caller.
Signed-off-by: Christoph Hellwig
---
drivers/ide/ide-cd.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/ide/ide-cd.c b/drivers/ide/ide-cd.c
index 6a38cbc80aea0d..25d2d88e82ada0 100644
---
The GD-ROM driver does not have a ->revalidate_disk method, so it can
just use bdev_check_media_change without any additional changes.
Signed-off-by: Christoph Hellwig
---
drivers/cdrom/gdrom.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cdrom/gdrom.c
OV8856 supports 3264x2448 @ 30 FPS, which is added
in this commit.
Signed-off-by: Robert Foss
---
drivers/media/i2c/ov8856.c | 215 +
1 file changed, 215 insertions(+)
diff --git a/drivers/media/i2c/ov8856.c b/drivers/media/i2c/ov8856.c
index
In file included from drivers/net/wireless/marvell/mwifiex//cmdevt.c:26:0:
drivers/net/wireless/marvell/mwifiex//wmm.h:41:17: warning: ‘tos_to_tid_inv’
defined but not used [-Wunused-const-variable=]
static const u8 tos_to_tid_inv[] = {
^~
On Wed 02-09-20 16:01:17, Michal Hocko wrote:
> [Cc Mel and Vlastimil - I am still rummaging]
>
> On Tue 01-09-20 08:46:15, Pavel Tatashin wrote:
> > There is a race during page offline that can lead to infinite loop:
> > a page never ends up on a buddy list and __offline_pages() keeps
> >
These variables only used in pcie.c, move them to .c file
can silence these warnings:
In file included from drivers/net/wireless/marvell/mwifiex/main.h:57:0,
from drivers/net/wireless/marvell/mwifiex/init.c:24:
drivers/net/wireless/marvell/mwifiex/pcie.h:310:41: warning:
On 11:34-20200831, santosh.shilim...@oracle.com wrote:
> On 8/29/20 11:41 AM, Grygorii Strashko wrote:
> > Hi Santosh,
> >
> > I've rebased on top of linux-next and identified merge conflict of patch 3
> > with commit 6da45875fa17 ("arm64: dts: k3-am65: Update the RM resource
> > types")
> > in
On Wed, Sep 02, 2020 at 03:24:19PM +0200, Antoni Przybylik wrote:
> This approach is more elegant and prevents some problems related to
> macros such as operator precedence in expanded expression.
> ---
> Changed return type to bool
On Tue, 1 Sep 2020 17:11:46 -0400
Darren Schachter wrote:
> On Sun, Aug 30, 2020 at 8:42 AM Jonathan Cameron wrote:
> >
> > On Tue, 18 Aug 2020 10:36:14 -0500
> > Darren Schachter wrote:
> >
> > > This IIO driver adds support for PWM capture with the TI eCAP module.
> > > This driver is
On Tue 01-09-20 08:46:15, Pavel Tatashin wrote:
> There is a race during page offline that can lead to infinite loop:
> a page never ends up on a buddy list and __offline_pages() keeps
> retrying infinitely or until a termination signal is received.
>
> Thread#1 - a new process:
>
>
Fix for TPROXY initialization of fastreuse flag.
upstream patch was backported by Greg K-H to 4.14 and higher stable version.
see also https://lore.kernel.org/stable/20200818072007.ga9...@kroah.com
code in inet_csk_get_port for 4.4 (and 4.9) is different from
the upstream version, so these
[ Upstream commit 62ffc589abb176821662efc4525ee4ac0b9c3894 ]
Refactor the fastreuse update code in inet_csk_get_port into a small
helper function that can be called from other places.
Acked-by: Matthieu Baerts
Signed-off-by: Tim Froidcoeur
Signed-off-by: David S. Miller
Signed-off-by: Tim
[ Upstream commit 62ffc589abb176821662efc4525ee4ac0b9c3894 ]
Refactor the fastreuse update code in inet_csk_get_port into a small
helper function that can be called from other places.
Acked-by: Matthieu Baerts
Signed-off-by: Tim Froidcoeur
Signed-off-by: David S. Miller
Signed-off-by: Tim
[ Upstream commit d76f3351cea2d927fdf70dd7c06898235035e84e ]
In the case of TPROXY, bind_conflict optimizations for SO_REUSEADDR or
SO_REUSEPORT are broken, possibly resulting in O(n) instead of O(1) bind
behaviour or in the incorrect reuse of a bind.
the kernel keeps track for each bind_bucket
match_string() returns the array index of a matching string.
Use it instead of the open-coded implementation.
Signed-off-by: YueHaibing
---
crypto/asymmetric_keys/pkcs7_verify.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/crypto/asymmetric_keys/pkcs7_verify.c
Fix for TPROXY initialization of fastreuse flag.
upstream patch was backported by Greg K-H to 4.14 and higher stable version.
see also https://lore.kernel.org/stable/20200818072007.ga9...@kroah.com/
code in inet_csk_get_port for 4.9 (and 4.4) is different from
the upstream version, so these
In case of error, the function perf_session__new() returns ERR_PTR()
and never returns NULL. The NULL test in the return value check
should be replaced with IS_ERR()
Fixes: 13edc237200c ("perf bench: Add a multi-threaded synthesize benchmark")
Signed-off-by: YueHaibing
---
In case of error, the function devm_ioremap_wc() returns NULL pointer
not ERR_PTR(). The IS_ERR() test in the return value check should be
replaced with NULL test.
Fixes: 87218f96c21a ("remoteproc: k3-dsp: Add support for C71x DSPs")
Signed-off-by: YueHaibing
---
[Cc Mel and Vlastimil - I am still rummaging]
On Tue 01-09-20 08:46:15, Pavel Tatashin wrote:
> There is a race during page offline that can lead to infinite loop:
> a page never ends up on a buddy list and __offline_pages() keeps
> retrying infinitely or until a termination signal is received.
>
[ Upstream commit d76f3351cea2d927fdf70dd7c06898235035e84e ]
In the case of TPROXY, bind_conflict optimizations for SO_REUSEADDR or
SO_REUSEPORT are broken, possibly resulting in O(n) instead of O(1) bind
behaviour or in the incorrect reuse of a bind.
the kernel keeps track for each bind_bucket
On 9/2/20 1:56 AM, pet...@infradead.org wrote:
> On Tue, Sep 01, 2020 at 08:51:46PM -0700, Guenter Roeck wrote:
>
>> [ 27.056457] include/trace/events/lock.h:13 suspicious
>> rcu_dereference_check() usage!
>
>> [ 27.057006] Hardware name: Generic OMAP3-GP (Flattened Device Tree)
>> [
From: Pawel Laszczak
USB2.0 PHY hangs in Rx Compliance test when the incoming packet
amplitude is varied below and above the Squelch Level of
Receiver during the active packet multiple times.
Version 1 of the controller allows PHY to be reset when RX fail condition
is detected to work around
On Wed, Sep 02, 2020 at 03:25:59PM +0200, Antoni Przybylik wrote:
> This approach is more elegant and prevents some problems related to
> macros such as operator precedence in expanded expression.
> ---
> Changed return type to bool
On Tue, Sep 01, 2020 at 11:11:37AM -0700, Dave Hansen wrote:
> On 9/1/20 10:45 AM, Andy Lutomirski wrote:
> >>> For arm64 (and sparc etc.) we continue to use the regular mmap/mprotect
> >>> family of calls. One or two additional arch-specific mmap flags are
> >>> sufficient for now.
> >>>
> >>>
On Wed, Sep 02, 2020 at 12:44:42PM +0200 Dietmar Eggemann wrote:
> + Phil Auld
>
Thanks Dietmar.
> On 28/08/2020 19:26, Qais Yousef wrote:
> > On 08/28/20 19:10, Dietmar Eggemann wrote:
> >> On 28/08/2020 12:27, Qais Yousef wrote:
> >>> On 08/28/20 10:00, vincent.donnef...@arm.com wrote:
>
On Mon 2020-08-31 03:16:57, John Ogness wrote:
> Use the record extending feature of the ringbuffer to implement
> continuous messages. This preserves the existing continuous message
> behavior.
>
> Signed-off-by: John Ogness
> ---
> kernel/printk/printk.c | 98
From: Christophe Leroy
> Sent: 02 September 2020 14:25
> Le 02/09/2020 à 15:13, David Laight a écrit :
> > From: Christoph Hellwig
> >> Sent: 02 September 2020 13:37
> >>
> >> On Wed, Sep 02, 2020 at 08:15:12AM +0200, Christophe Leroy wrote:
> -return 0;
> -return
Le 02/09/2020 à 15:13, David Laight a écrit :
From: Christoph Hellwig
Sent: 02 September 2020 13:37
On Wed, Sep 02, 2020 at 08:15:12AM +0200, Christophe Leroy wrote:
- return 0;
- return (size == 0 || size - 1 <= seg.seg - addr);
+ if (addr >= TASK_SIZE_MAX)
+
On Wed 02-09-20 08:51:06, Pavel Tatashin wrote:
> > > > Thread #1: memory hot-remove systemd service
> > > > Loops indefinitely, because if there is something still to be migrated
> > > > this loop never terminates. However, this loop can be terminated via
> > > > signal from systemd after
Le 02/09/2020 à 15:02, Ivan Mikhaylov a écrit :
Hello everyone. Currently, the watchdog interface only has "stop watchdog on
restart" but lacks a "start watchdog on restart" one. Is there a way to achieve
such functionality?
I'd like to know why "stop watchdog on restart" wasn't implemented
On Wed 02-09-20 08:42:13, Pavel Tatashin wrote:
> > > Am 02.09.2020 um 11:53 schrieb Vlastimil Babka :
> > >
> > > On 8/28/20 6:47 PM, Pavel Tatashin wrote:
> > >> There appears to be another problem that is related to the
> > >> cgroup_mutex -> mem_hotplug_lock deadlock described above.
> > >>
>
On Tue, Sep 01, 2020 at 09:55:48PM +0100, Ionela Voinescu wrote:
> From: Valentin Schneider
>
> The passed cpumask arguments to arch_set_freq_scale() and
> arch_freq_counters_available() are only iterated over, so reflect this
> in the prototype. This also allows to pass system cpumasks like
>
On Tue, Sep 01, 2020 at 09:55:49PM +0100, Ionela Voinescu wrote:
> From: Valentin Schneider
>
> arch_scale_freq_invariant() is used by schedutil to determine whether
> the scheduler's load-tracking signals are frequency invariant. Its
> definition is overridable, though by default it is
On Tue, Sep 01, 2020 at 05:40:49PM +0200, Christoph Hellwig wrote:
> On Tue, Sep 01, 2020 at 05:36:17PM +0200, Ulf Hansson wrote:
> > > I still don't think this makes sense, as the dma_mask should always
> > > be non-NULL here.
> >
> > If that is the case, I wonder how the driver could even have
On Mon, Aug 31, 2020 at 09:35:19PM -0400, wrote:
> On Mon, Aug 31, 2020 at 10:35:12AM -0700, Jesse Brandeburg wrote:
> > Thanks for the report Lennart, I understand your frustration, as this
> > should probably work without user configuration.
> >
> > However, please give this command a try:
> >
On Wed, Sep 02, 2020 at 02:21:27PM +0100, Leo Yan wrote:
> The system register CNTVCT_EL0 can be used to retrieve the counter from
> user space. Add rdtsc() for Arm64.
> +u64 rdtsc(void)
> +{
> + u64 val;
Would it make sense to put a comment in that this counter is/could-be
'short' ?
On 9/2/20 2:12 AM, pet...@infradead.org wrote:
> On Wed, Sep 02, 2020 at 11:09:35AM +0200, pet...@infradead.org wrote:
>> On Tue, Sep 01, 2020 at 09:21:37PM -0700, Guenter Roeck wrote:
>>> [0.00] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:4875
>>> check_flags.part.39+0x280/0x2a0
There's no point in calculating si_code if we're not going to use it.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/kernel/traps.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
--- a/arch/x86/kernel/traps.c
+++ b/arch/x86/kernel/traps.c
@@ -786,15 +786,14 @@
This is called with interrupts disabled, there's no point in using
get_cpu() and per_cpu().
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/kernel/hw_breakpoint.c |8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
--- a/arch/x86/kernel/hw_breakpoint.c
+++
Unused remnants for the bit-bucket.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/debugreg.h |2 --
arch/x86/kernel/hw_breakpoint.c | 36
2 files changed, 38 deletions(-)
--- a/arch/x86/include/asm/debugreg.h
+++
On Tue, 21 Jul 2020, Joe Lawrence wrote:
> The livepatch samples aren't very careful with respect to compiler
> IPA-optimization of target kernel functions.
>
> Add a quick disclaimer and pointer to the compiler-considerations.rst
> file to warn readers.
>
> Suggested-by: Josh Poimboeuf
>
On Wed, 2020-09-02 at 11:42 +, Roberto Sassu wrote:
> > From: Mimi Zohar [mailto:zo...@linux.ibm.com]
> > Sent: Monday, August 24, 2020 7:45 PM
> > Hi Roberto,
> >
> > On Fri, 2020-08-21 at 14:30 -0400, Mimi Zohar wrote:
> > > Sorry for the delay in reviewing these patches. Missing from
On Wed, 2 Sep 2020 15:35:45 +0200
Krzysztof Kozlowski wrote:
> On Wed, 2 Sep 2020 at 15:28, Jonathan Cameron
> wrote:
> >
> > On Wed, 2 Sep 2020 10:49:04 +0300
> > Andy Shevchenko wrote:
> >
> > > On Wed, Sep 2, 2020 at 8:56 AM Ardelean, Alexandru
> > > wrote:
> > > >
> > > > [yes, I
On Wed, Sep 02, 2020 at 08:26:42PM +0800, Ming Lei wrote:
> 'struct percpu_ref' is often embedded into one user structure, and the
> instance is usually referenced in fast path, however actually only
> 'percpu_count_ptr' is needed in fast path.
>
> So move other fields into one new structure of
On Wed, Sep 02, 2020 at 10:19:26PM +0900, Masami Hiramatsu wrote:
> On Wed, 2 Sep 2020 11:36:13 +0200
> pet...@infradead.org wrote:
>
> > On Wed, Sep 02, 2020 at 05:17:55PM +0900, Masami Hiramatsu wrote:
> >
> > > > Ok, but then lockdep will yell at you if you have that enabled and run
> > > >
On Wed, 2 Sep 2020 12:28:02 +0300
Andy Shevchenko wrote:
> On Wed, Sep 2, 2020 at 12:12 PM Hennerich, Michael
> wrote:
> > > From: Andy Shevchenko
> > > Sent: Mittwoch, 2. September 2020 10:52
> > > On Wed, Sep 2, 2020 at 11:09 AM Hennerich, Michael
> > > wrote:
>
> ...
>
> > > I see. Can
This patch fixes the device name typo.
Fixes: 951ad4700313 ("iio: adc: ad7124: move chip ID & name on the chip_info
table")
Signed-off-by: Mircea Caprioru
---
drivers/iio/adc/ad7124.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iio/adc/ad7124.c
Current usage of thread.debugreg6 is convoluted at best. It starts
life as a copy of the hardware DR6 value, but then we clear and set
various bits.
Replace this with a new variable thread.virtual_dr6 that is
initialized to 0 when we read DR6 and only gains bits, at the same
time the actual (on
From: Peter Zijlstra
The WARN added in commit 3c73b81a9164 ("x86/entry, selftests: Further
improve user entry sanity checks") unconditionally triggers on my IVB
machine because it does not support SMAP.
For !SMAP hardware we patch out CLAC/STAC instructions and thus if
userspace sets AC, we'll
The system register CNTVCT_EL0 can be used to retrieve the counter from
user space. Add rdtsc() for Arm64.
Signed-off-by: Leo Yan
---
tools/perf/arch/arm64/util/Build | 1 +
tools/perf/arch/arm64/util/tsc.c | 14 ++
2 files changed, 15 insertions(+)
create mode 100644
Hi Hoegeun
On Fri, Aug 21, 2020 at 04:18:34PM +0900, Hoegeun Kwon wrote:
> Hi Maxime,
>
> Thank you for your version 4 patch.
> I tested all 78 patches based on the next-20200708.
>
>
> Dual HDMI opearation does not work normally.
> flip_done timed out occurs and doesn't work.
> Could you
This approach is more elegant and prevents some problems related to
macros such as operator precedence in expanded expression.
---
Changed return type to bool and removed inline sepcifier.
Signed-off-by: Antoni Przybylik
---
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9c7d619be5a002ea29c172df5e3c1227c22cbb41
commit: 203b1152d18c04823f73b843eb3b0ad646e4dbb2 arm64/crash_core: Export
KERNELPACMASK in vmcoreinfo
date: 4 months ago
config: arm64-randconfig-s031-20200902
On Wed, Sep 02, 2020 at 12:43:48PM +0100, Mark Rutland wrote:
> I'll see what I can do.
>
> At first glance it looks like we might need to flesh out or refactor the
> arm64 kernel maccess routines first (since we want the user maccess
> routines to use LDTR/STTR instructions that can't access
Functions perf_read_tsc_conversion() and perf_event__synth_time_conv()
should work as common functions rather than x86 specific, so move these
two functions out from arch/x86 folder and place them into util/tsc.c.
Since the function perf_event__synth_time_conv() will be linked in
util/tsc.c,
The synthesized event TIME_CONV doesn't contain the complete parameters
for counters, this will lead to wrong conversion between counter cycles
and timestamp.
This patch extends event TIME_CONV to record flags 'cap_user_time_zero'
which is used to indicate the counter parameters are valid or not,
This approach is more elegant and prevents some problems related to
macros such as operator precedence in expanded expression.
---
Changed return type to bool and removed inline sepcifier.
Signed-off-by: Antoni Przybylik
---
Peter,
On 27/08/2020 14:14, Peter Chen wrote:
On 20-08-25 15:00:58, Roger Quadros wrote:
Controller version 0x0002450D has USB2 PHY RX sensitivity issues
that needs to be worked around by enabling phyrst-a-enable bit
in PHYRST_CFG register.
There is no way to distinguish between the
On Mon, 31 Aug 2020 at 13:28, Konrad Dybcio wrote:
>
> > Hi Konrad,
> >
> > I couldn't find answer to your question around missing
> > (regulatorname)-supply properties. Need help in figuring out that
> > part.
>
> When the phone boots up and RPM(H) kicks in, you should see regulators
> probing
On Wed, 2 Sep 2020 10:49:04 +0300
Andy Shevchenko wrote:
> On Wed, Sep 2, 2020 at 8:56 AM Ardelean, Alexandru
> wrote:
> >
> > [yes, I know, bad-email format, but I wanted this to come from my work
> > email]
> >
> > Apologies also for the delay here. Things pile-up on my side and I defer
> >
From: Christoph Hellwig
> Sent: 02 September 2020 13:37
>
> On Wed, Sep 02, 2020 at 08:15:12AM +0200, Christophe Leroy wrote:
> >> - return 0;
> >> - return (size == 0 || size - 1 <= seg.seg - addr);
> >> + if (addr >= TASK_SIZE_MAX)
> >> + return false;
> >> + if (size == 0)
On Wed, Sep 02, 2020 at 12:23:10PM +, Harley Paterson wrote:
> Most PID functions in `kernel/pid.c` are named in the format
> [do_something]_pid, and functions with a VPID counterpart have
> the corresponding name [do_something]_vpid.
>
> `find_get_pid` and its VPID counterpart, `find_ge_pid`
Hi Matthias,
On 2020-08-21 21:56, Matthias Kaehlcke wrote:
On Thu, Aug 20, 2020 at 07:21:05PM +0530, satya priya wrote:
Add the necessary pinctrl and interrupts to make UART
wakeup capable.
Signed-off-by: satya priya
Reviewed-by: Akash Asthana
---
Changes in V2:
- As per Matthias's comment
> -Original Message-
> From: linux-crypto-ow...@vger.kernel.org
> On Behalf Of Denis Efremov
> Sent: Thursday, August 27, 2020 8:44 AM
> To: linux-cry...@vger.kernel.org
> Cc: Denis Efremov ; Corentin Labbe
> ; Herbert Xu
> ; linux-kernel@vger.kernel.org
> Subject: [PATCH v2 1/4]
If the zero duty cycle doesn't correspond to any voltage in the voltage
table, the PWM regulator returns an -EINVAL from get_voltage_sel() which
results in the core erroring out with a "failed to get the current
voltage" and ending up not applying the machine constraints.
Instead, return
Hello everyone. Currently, the watchdog interface only has "stop watchdog on
restart" but lacks a "start watchdog on restart" one. Is there a way to achieve
such functionality?
I'd like to know why "stop watchdog on restart" wasn't implemented via ioctl
interface? It would be more convenient from
Replace all '/* fall through */' comments with the macro[1].
[1]:
https://www.kernel.org/doc/html/v5.7/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through
Signed-off-by: Leesoo Ahn
---
.../net/wireless/ralink/rt2x00/rt2400pci.c| 3 ++-
It's not desireable to have all MSRs always handled by KVM kernel space. Some
MSRs would be useful to handle in user space to either emulate behavior (like
uCode updates) or differentiate whether they are valid based on the CPU model.
To allow user space to specify which MSRs it wants to see
Now that we have the ability to handle MSRs from user space and also to
select which ones we do want to prevent in-kernel KVM code from handling,
let's add a selftest to show case and verify the API.
Signed-off-by: Alexander Graf
---
v2 -> v3:
-
MSRs are weird. Some of them are normal control registers, such as EFER.
Some however are registers that really are model specific, not very
interesting to virtualization workloads, and not performance critical.
Others again are really just windows into package configuration.
Out of these MSRs,
On 02.09.20 00:32, Aaron Lewis wrote:
On Tue, Sep 1, 2020 at 1:15 PM Alexander Graf wrote:
While tying to add support for the MSR_CORE_THREAD_COUNT MSR in KVM,
I realized that we were still in a world where user space has no control
over what happens with MSR emulation in KVM.
That is bad
We will introduce the concept of MSRs that may not be handled in kernel
space soon. Some MSRs are directly passed through to the guest, effectively
making them handled by KVM from user space's point of view.
This patch introduces all logic required to ensure that MSRs that
user space wants
From: Aaron Lewis
Prepare vmx and svm for a subsequent change that ensures the MSR permission
bitmap is set to allow an MSR that userspace is tracking to force a vmx_vmexit
in the guest.
Signed-off-by: Aaron Lewis
Reviewed-by: Oliver Upton
Signed-off-by: Alexander Graf
---
We will introduce the concept of MSRs that may not be handled in kernel
space soon. Some MSRs are directly passed through to the guest, effectively
making them handled by KVM from user space's point of view.
This patch introduces all logic required to ensure that MSRs that
user space wants
In the following commits we will add pieces of MSR filtering.
To ensure that code compiles even with the feature half-merged, let's add
a few stubs and struct definitions before the real patches start.
Signed-off-by: Alexander Graf
---
arch/x86/include/asm/kvm_host.h | 1 +
While tying to add support for the MSR_CORE_THREAD_COUNT MSR in KVM,
I realized that we were still in a world where user space has no control
over what happens with MSR emulation in KVM.
That is bad for multiple reasons. In my case, I wanted to emulate the
MSR in user space, because it's a CPU
Hi!
> The syzbot fuzzer identified a bug in the yurex driver: It passes
> GFP_KERNEL as a memory-allocation flag to usb_submit_urb() at a time
> when its state is TASK_INTERRUPTIBLE, not TASK_RUNNING:
Yeah, and instead of fixing the bug, patch papers over it, reducing
reliability of the driver
elay() with fsleep(), which is flexible sleep function that
>> selects best delay function based on the delay-time.
>>
>> Signed-off-by: Dmitry Osipenko
>
> This patch landed in today's linux-next (20200902) as commit
> 2b32d2f7ce0a. Sadly it breaks booting of ARM 64bit A
On Wed, Sep 2, 2020 at 7:32 AM Michal Hocko wrote:
>
> On Wed 02-09-20 11:53:00, Vlastimil Babka wrote:
> > >> > > Thread #2: ccs killer kthread
> > >> > >css_killed_work_fn
> > >> > > cgroup_mutex <- Grab this Mutex
> > >> > > mem_cgroup_css_offline
> > >> > >
From: Lai Jiangshan
When kvm_mmu_get_page() gets a page with unsynced children, the spt
pagetable is unsynchronized with the guest pagetable. But the
guest might not issue a "flush" operation on it when the pagetable
entry is changed from zero or other cases. The hypervisor has the
On Tue, Sep 01, 2020 at 09:18:57AM -0700, Nadav Amit wrote:
> Unless I misunderstand the logic, __force_order should also be used by
> rdpkru() and wrpkru() which do not have dependency on __force_order. I
> also did not understand why native_write_cr0() has R/W dependency on
> __force_order, and
On Thu, Aug 06, 2020 at 05:43:26PM +, Uriel Guajardo wrote:
> Integrates UBSAN into the KUnit testing framework. It fails KUnit tests
> whenever it reports undefined behavior.
>
> Signed-off-by: Uriel Guajardo
It looks like this patch had been merged into linux-next but the "[PATCH 1/2]
Dear Sir/Madam,
We are an Investment/Project Service Company.
We are looking for Partners that will part with us in a project that is
economically viable and financially profitable with zero risk.
Kindly express your interest to partner with us.
Regards.
Nassir Uddin
Hi Pavel,
On Wed, Sep 02, 2020 at 12:25:21PM +0200, Pavel Machek wrote:
> Hi!
> >
> > [ Upstream commit ea8912b788f8144e7d32ee61e5ccba45424bef83 ]
> >
> > usleep_range() may take longer than the max argument due to scheduling,
> > especially under load. This is causing random errors in the
> > > Thread #1: memory hot-remove systemd service
> > > Loops indefinitely, because if there is something still to be migrated
> > > this loop never terminates. However, this loop can be terminated via
> > > signal from systemd after timeout.
> > > __offline_pages()
> > > do {
> > >
Hi,
It is mainly due to the business priority change. XenGT project was originally
created for data center usages with XEON E3 servers which have integrated
processor graphics. After SkyLake E3, there are no new servers capable of
running GVT-g, and Intel future graphics for data center will
On Wed, Sep 02, 2020 at 08:37:15PM +0800, Boqun Feng wrote:
> On Wed, Sep 02, 2020 at 12:14:12PM +0200, pet...@infradead.org wrote:
> > > To be accurate, atomic_set() doesn't return any value, so it cannot be
> > > ordered against DR and DW ;-)
> >
> > Surely DW is valid for any store.
> >
>
>
s best delay function based on the delay-time.
>
> Signed-off-by: Dmitry Osipenko
This patch landed in today's linux-next (20200902) as commit
2b32d2f7ce0a. Sadly it breaks booting of ARM 64bit Amlogic S922X based
Odroid N2 board. Here is the log:
BUG: scheduling while atomic: kworker/4
On September 1, 2020 9:18:57 AM PDT, Nadav Amit wrote:
>From: Nadav Amit
>
>The __force_order logic seems to be inverted. __force_order is
>supposedly used to manipulate the compiler to use its memory
>dependencies analysis to enforce orders between CR writes and reads.
>Therefore, the memory
On Tue, Sep 01, 2020 at 03:59:12PM -0700, Florian Fainelli wrote:
> Fetch the corresponding clock resource and enable/disable it during
> suspend/resume if and only if we have no ports defined for Wake-on-LAN.
>
> Signed-off-by: Florian Fainelli
Reviewed-by: Andrew Lunn
Andrew
On Tue, Sep 01, 2020 at 03:59:13PM -0700, Florian Fainelli wrote:
> Whenever a port gets enabled/disabled, recalcultate the required switch
> clock rate to make sure it always gets set to the expected rate
> targeting our switch use case. This is only done for the BCM7445 switch
> as there is no
On Tue, Sep 01, 2020 at 03:59:11PM -0700, Florian Fainelli wrote:
> Describe the two possible clocks feeding into the Broadcom SF2
> integrated Ethernet switch. BCM7445 systems have two clocks, one for the
> main switch core clock, and another for controlling the switch clock
> divider whereas
> > Am 02.09.2020 um 11:53 schrieb Vlastimil Babka :
> >
> > On 8/28/20 6:47 PM, Pavel Tatashin wrote:
> >> There appears to be another problem that is related to the
> >> cgroup_mutex -> mem_hotplug_lock deadlock described above.
> >>
> >> In the original deadlock that I described, the
On Wed 2020-09-02 13:26:14, John Ogness wrote:
> On 2020-09-02, Petr Mladek wrote:
> >> +static struct prb_desc *desc_reopen_last(struct prb_desc_ring *desc_ring,
> >> + u32 caller_id, unsigned long *id_out)
> >> +{
> >> + unsigned long prev_state_val;
> >> +
On Wed, Sep 02, 2020 at 08:15:12AM +0200, Christophe Leroy wrote:
>> -return 0;
>> -return (size == 0 || size - 1 <= seg.seg - addr);
>> +if (addr >= TASK_SIZE_MAX)
>> +return false;
>> +if (size == 0)
>> +return false;
>
> __access_ok() was
On Wed, Sep 02, 2020 at 12:14:12PM +0200, pet...@infradead.org wrote:
> On Wed, Sep 02, 2020 at 11:54:48AM +0800, Boqun Feng wrote:
> > On Mon, Aug 31, 2020 at 11:20:34AM -0700, paul...@kernel.org wrote:
> > > From: "Paul E. McKenney"
> > >
> > > This commit adds a key entry enumerating the
901 - 1000 of 1333 matches
Mail list logo
