From: Andrew Cooper <andrew.cooper3@citrix.com>
To: John McDermott <John.McDermott@nrl.navy.mil>
Cc: xen-devel@lists.xenproject.org
Subject: Re: Xen 4.4 Testing: Platform Op XENPF_microcode_update Leaves VCPU Lock Set?
Date: Thu, 24 Apr 2014 15:10:16 +0100 [thread overview]
Message-ID: <53591B48.7030004@citrix.com> (raw)
In-Reply-To: <8EF1AEBB-898F-4CA3-812A-F9FAA29A9D03@nrl.navy.mil>
On 24/04/14 14:35, John McDermott wrote:
> Xen Developers,
>
> In arch/x86/platform_hypercall.c, in function do_platform_op, the case XENPF_microcode_update appears to leave the vcpu_alloc_lock set when creating a hypercall continuation, but I don't understand the hypercall continuation code as releasing that lock. The lock is not released at target label of the following goto, in case XENPF_microcode_update.
>
> I don't have the facilities to exercise this case on my development platform, but it looks like a possible problem or does the hypercall continuation somehow take care of this lock?
>
> Sincerely,
>
> John
spin_trylock() will try to take the spinlock, but return failure rather
than spinning.
The body of the while loop is therefore strictly when the
vcpu_alloc_lock is not held, so the goto out is safe in context.
>
> ps. I tried subscribing to the Xen dev list 3 times but it never worked.
That is curious. Any indication of an error? You certainly havn't
successfully signed up as I had to approve this email through moderation.
~Andrew
next prev parent reply other threads:[~2014-04-24 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 13:35 Xen 4.4 Testing: Platform Op XENPF_microcode_update Leaves VCPU Lock Set? John McDermott
2014-04-24 14:10 ` Ian Campbell
2014-04-24 16:39 ` John McDermott
2014-04-24 14:10 ` Andrew Cooper [this message]
2014-04-24 16:36 ` John McDermott
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=53591B48.7030004@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=John.McDermott@nrl.navy.mil \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.