From: J Ahn <jeong.seob.ahn@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: How to handle TLB shootdown IPI on Xen
Date: Tue, 13 Aug 2013 01:50:33 +0900 [thread overview]
Message-ID: <CAFgwMgqq8vJPx2CDyfaB+W43T=roE-o6jbw1nmYFJ3tYgKFrWA@mail.gmail.com> (raw)
In-Reply-To: <5209286402000078000EB527@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]
2013/8/13 Jan Beulich <JBeulich@suse.com>
> >>> On 12.08.13 at 18:04, J Ahn <jeong.seob.ahn@gmail.com> wrote:
> > I was wondering how Xen works when the guest sends the TLB shootdown IPI.
> > You mean that there is no need to intercept the IPI on Xen.
> > Is my understanding right?
>
> Xen is just involved in the delivery of the virtual interrupt, but
> doesn't participate in its handling.
>
> Jan
>
>
As I mentioned the first post, I also guess that the hypervisor
intervention is required to route the virtual IPI.
So, I would like to know where the delivery code on Xen has been located
because I could not find the delivery point for the virtual IPI.
Does the *vmx_do_extint()* function delivery the IPI through *
__do_IRQ_guest()* ??
Thank you for your kind advice.
[-- Attachment #1.2: Type: text/html, Size: 1556 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-12 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 16:22 How to handle TLB shootdown IPI on Xen J Ahn
2013-08-12 8:36 ` Jan Beulich
2013-08-12 12:47 ` J Ahn
2013-08-12 13:29 ` Jan Beulich
2013-08-12 16:04 ` J Ahn
2013-08-12 16:24 ` Jan Beulich
2013-08-12 16:50 ` J Ahn [this message]
2013-08-13 10:16 ` Jan Beulich
2013-08-13 13:16 ` J Ahn
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='CAFgwMgqq8vJPx2CDyfaB+W43T=roE-o6jbw1nmYFJ3tYgKFrWA@mail.gmail.com' \
--to=jeong.seob.ahn@gmail.com \
--cc=JBeulich@suse.com \
--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.