From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 02/14] Nested Virtualization: localevent
Date: Thu, 5 Aug 2010 17:19:14 +0100 [thread overview]
Message-ID: <C880A312.1CE4D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C8809B4C.1CE41%keir.fraser@eu.citrix.com>
I seem to remember we discussed the reason for this a bit some time ago. It
looked to me like you were calling a function that makes sense only on a
running guest (and a locally currently running guest at that) after the
guest was dead, during cleanup/teardown. If I'm remebering correctly then
the fix would be to not do that then. ;-)
-- Keir
On 05/08/2010 16:46, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
> The functions are called local_event_delivery* because they implicitly act
> on current. They don't need to take a vcpu parameter. If you find you need a
> vcpu parameter then you are using them, or one of their callers,
> incorrectly.
>
> -- Keir
>
> On 05/08/2010 16:00, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
>
>>
>> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-08-05 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 15:00 [PATCH 02/14] Nested Virtualization: localevent Christoph Egger
2010-08-05 15:46 ` Keir Fraser
2010-08-05 16:19 ` Keir Fraser [this message]
2010-08-06 9:17 ` Christoph Egger
2010-08-06 14:02 ` Keir Fraser
2010-08-10 8:01 ` Christoph Egger
2010-08-10 8:21 ` Keir Fraser
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=C880A312.1CE4D%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).