mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
	x86@kernel.org
Cc: boris.ostrovsky@oracle.com, sstabellini@kernel.org,
	hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, stable@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen: fix xen_qlock_wait()
Date: Fri, 9 Nov 2018 16:20:29 +0100	[thread overview]
Message-ID: <068f9560-598b-0228-463b-bc7f202cf8e0@suse.com> (raw)
In-Reply-To: <400409f5-397e-780b-d13b-19a1ee578f44@eikelenboom.it>

On 09/11/2018 16:02, Sander Eikelenboom wrote:
> On 09/11/18 13:04, Juergen Gross wrote:
>> Commit a856531951dc80 ("xen: make xen_qlock_wait() nestable")
>> introduced a regression for Xen guests running fully virtualized
>> (HVM or PVH mode). The Xen hypervisor wouldn't return from the poll
>> hypercall with interrupts disabled in case of an interrupt (for PV
>> guests it does).
>>
>> So instead of disabling interrupts in xen_qlock_wait() use a nesting
>> counter to avoid calling xen_clear_irq_pending() in case
>> xen_qlock_wait() is nested.
>>
>> Fixes: a856531951dc80 ("xen: make xen_qlock_wait() nestable")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Juergen Gross <jgross@suse.com>
> 
> Although you don't seem too interested, you can stick on a:
> Tested-by: Sander Eikelenboom <linux@eikelenboom.it>
> if you like.

I am interested.

OTOH I wanted to post the patch officially to give others the chance to
send remarks.


Juergen

> 
> --
> Sander
> 
>> ---
>>  arch/x86/xen/spinlock.c | 14 ++++++++------
>>  1 file changed, 8 insertions(+), 6 deletions(-)
>>
>> diff --git a/arch/x86/xen/spinlock.c b/arch/x86/xen/spinlock.c
>> index 441c88262169..1c8a8816a402 100644
>> --- a/arch/x86/xen/spinlock.c
>> +++ b/arch/x86/xen/spinlock.c
>> @@ -9,6 +9,7 @@
>>  #include <linux/log2.h>
>>  #include <linux/gfp.h>
>>  #include <linux/slab.h>
>> +#include <linux/atomic.h>
>>  
>>  #include <asm/paravirt.h>
>>  #include <asm/qspinlock.h>
>> @@ -21,6 +22,7 @@
>>  
>>  static DEFINE_PER_CPU(int, lock_kicker_irq) = -1;
>>  static DEFINE_PER_CPU(char *, irq_name);
>> +static DEFINE_PER_CPU(atomic_t, xen_qlock_wait_nest);
>>  static bool xen_pvspin = true;
>>  
>>  static void xen_qlock_kick(int cpu)
>> @@ -39,25 +41,25 @@ static void xen_qlock_kick(int cpu)
>>   */
>>  static void xen_qlock_wait(u8 *byte, u8 val)
>>  {
>> -	unsigned long flags;
>>  	int irq = __this_cpu_read(lock_kicker_irq);
>> +	atomic_t *nest_cnt = this_cpu_ptr(&xen_qlock_wait_nest);
>>  
>>  	/* If kicker interrupts not initialized yet, just spin */
>>  	if (irq == -1 || in_nmi())
>>  		return;
>>  
>> -	/* Guard against reentry. */
>> -	local_irq_save(flags);
>> +	/* Detect reentry. */
>> +	atomic_inc(nest_cnt);
>>  
>> -	/* If irq pending already clear it. */
>> -	if (xen_test_irq_pending(irq)) {
>> +	/* If irq pending already and no nested call clear it. */
>> +	if (atomic_read(nest_cnt) == 1 && xen_test_irq_pending(irq)) {
>>  		xen_clear_irq_pending(irq);
>>  	} else if (READ_ONCE(*byte) == val) {
>>  		/* Block until irq becomes pending (or a spurious wakeup) */
>>  		xen_poll_irq(irq);
>>  	}
>>  
>> -	local_irq_restore(flags);
>> +	atomic_dec(nest_cnt);
>>  }
>>  
>>  static irqreturn_t dummy_handler(int irq, void *dev_id)
>>
> 
> 


  reply	other threads:[~2018-11-09 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 12:04 Juergen Gross
2018-11-09 14:53 ` Boris Ostrovsky
2018-11-09 15:02 ` [Xen-devel] " Sander Eikelenboom
2018-11-09 15:20   ` Juergen Gross [this message]
2018-11-09 15:29     ` Sander Eikelenboom
2018-11-09 15:35       ` Juergen Gross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=068f9560-598b-0228-463b-bc7f202cf8e0@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    --cc=mingo@redhat.com \
    --cc=sstabellini@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®