Re: [PATCH] docs: Do not include from kernel/rcu/srcu.c

On Tue, Jul 04, 2017 at 01:26:47PM -0600, Jonathan Corbet wrote: > That file went away with commit bd8cc5a062f4 (srcu: Remove Classic SRCU) > during the 4.13 merge window, leading to errors like: > > Error: Cannot open file ./kernel/rcu/srcu.c > > during the docs build. > > Reported-by: Linus

[PATCH] docs: Do not include from kernel/rcu/srcu.c

That file went away with commit bd8cc5a062f4 (srcu: Remove Classic SRCU) during the 4.13 merge window, leading to errors like: Error: Cannot open file ./kernel/rcu/srcu.c during the docs build. Reported-by: Linus Torvalds Signed-off-by: Jonathan Corbet

Re: [PULL] Docs for 4.13

On Mon, 3 Jul 2017 21:32:33 -0700 Linus Torvalds wrote: > Eg things like > > Error: Cannot open file ./kernel/rcu/srcu.c > Error: Cannot open file ./kernel/rcu/srcu.c > > happen simply because that file no longer exists, and the docs never > got updated. > >

Re: [PATCH 2/2] x86/idle: use dynamic halt poll

On Tue, 4 Jul 2017, Radim Krčmář wrote: > I think there is a nicer solution to avoid the expensive timer rewrite: > Linux uses one-shot APIC timers and getting the timer interrupt is about > as expensive as programming the timer, so the guest can keep the timer > armed, but not re-arm it after the

Re: [PATCH 2/2] x86/idle: use dynamic halt poll

2017-07-03 17:28+0800, Yang Zhang: > The background is that we(Alibaba Cloud) do get more and more complaints > from our customers in both KVM and Xen compare to bare-mental.After > investigations, the root cause is known to us: big cost in message passing > workload(David show it in KVM forum

Re: [PATCH v4 3/3] arm64: kvm: inject SError with user space specified syndrome

Hi James, Thanks for the review. I will read your comments carefully and then reply to you. On 2017/7/4 18:14, James Morse wrote: > Hi gengdongjiu, > > Can you give us a specific example of an error you are trying to handle? > How would a non-KVM user space process handle the error? > >

Re: [PATCH v4 3/3] arm64: kvm: inject SError with user space specified syndrome

Hi gengdongjiu, Can you give us a specific example of an error you are trying to handle? How would a non-KVM user space process handle the error? KVM-users should be regular user space processes, we should not have a KVM-way and everyone-else-way of handling errors. On 04/07/17 05:46,

Re: [PATCH v4 3/3] arm64: kvm: inject SError with user space specified syndrome

Hi Dongjiu, On Tue, Jul 04, 2017 at 12:46:23PM +0800, gengdongjiu wrote: > Hi Christoffer, > thanks for the review. > > > On 2017/7/3 16:39, Christoffer Dall wrote: > > Hi Dongjiu, > > > > On Mon, Jun 26, 2017 at 08:46:39PM +0800, Dongjiu Geng wrote: > >> when SError happen, kvm notifies

Re: [PATCH v4 2/3] arm64: kvm: route synchronous external abort exceptions to el2

Hi Dongjiu, On Tue, Jul 04, 2017 at 02:30:21PM +0800, gengdongjiu wrote: > Hi Christoffer, > > On 2017/7/3 16:23, Christoffer Dall wrote: > > On Tue, Jun 27, 2017 at 08:15:49PM +0800, gengdongjiu wrote: > >> correct the commit message: > >> > >> In the firmware-first RAS solution, OS receives

Re: [PATCH v4 1/3] arm64: kvm: support user space to detect RAS extension feature

Hi Dongjiu, On Tue, Jul 04, 2017 at 03:04:54PM +0800, gengdongjiu wrote: > Hi Christoffer, > > On 2017/7/3 16:21, Christoffer Dall wrote: > > On Mon, Jun 26, 2017 at 08:45:43PM +0800, Dongjiu Geng wrote: > >> Handle userspace's detection for RAS extension, because sometimes > >> the userspace

Re: [PULL] Docs for 4.13

Hi Jon, > Am 04.07.2017 um 06:32 schrieb Linus Torvalds : [...] > At the same time, lots of people run a lot of builds, and while I'd > love to see warnings about docs failures, I am *not* willing to slow > down my usual build enormously. I run "male allmodconfig"

[PATCH] Docs: add 'lintdocs' target with basic sanity checks

From: Markus Heiser The 'lintdocs' produces no output. The input is only parsed and checked for consistency. This is useful for basic sanity checks [1]. The 'lintdocs' target uses Sphinx's 'dummy' builder. For this at least Sphinx 1.4 is needed [2]. Sphinx 1.4 is not

Re: [PATCH v4 1/3] arm64: kvm: support user space to detect RAS extension feature

Hi Christoffer, On 2017/7/3 16:21, Christoffer Dall wrote: > On Mon, Jun 26, 2017 at 08:45:43PM +0800, Dongjiu Geng wrote: >> Handle userspace's detection for RAS extension, because sometimes >> the userspace needs to know the CPU's capacity > > Why? Can you please provide some more rationale.

Re: [PATCH v4 2/3] arm64: kvm: route synchronous external abort exceptions to el2

Hi Christoffer, On 2017/7/3 16:23, Christoffer Dall wrote: > On Tue, Jun 27, 2017 at 08:15:49PM +0800, gengdongjiu wrote: >> correct the commit message: >> >> In the firmware-first RAS solution, OS receives an synchronous >> external abort, then trapped to EL3 by SCR_EL3.EA. Firmware inspects