From: Keir Fraser <keir.xen@gmail.com>
To: wei.huang2@amd.com, xen-devel@lists.xen.org,
Jan Beulich <JBeulich@suse.com>
Subject: Re: LWP Interrupt Handler
Date: Fri, 23 Mar 2012 22:49:48 +0000 [thread overview]
Message-ID: <CB92AE8C.2F427%keir.xen@gmail.com> (raw)
In-Reply-To: <4F6CF344.30802@amd.com>
On 23/03/2012 22:03, "Wei Huang" <wei.huang2@amd.com> wrote:
> I am adding interrupt support for LWP, whose spec is available at
> http://support.amd.com/us/Processor_TechDocs/43724.pdf. Basically OS can
> specify an interrupt vector in LWP_CFG MSR; the interrupt will be
> triggered when event buffer overflows. For HVM guests, I want to
> re-inject this interrupt back into the guest VM. Here is one idea
> similar to virtualized PMU: It first registers a special interrupt
> handler (say on vector 0xf6) using set_intr_gate(). When triggered, this
> handler injects an IRQ (with vector copied from LWP_CFG) into guest VM
> via virtual local APIC. This worked from my test.
>
> But adding a interrupt handler seems to be an overkill. Is there any
> better way to create a dummy interrupt receiver on be-behalf of guest
> VMs? I also looked into IRQ and MSI solutions inside Xen. But most of
> them assume that interrupts are from physical device (but not in this
> LWP case, where interrupt is initiated from CPU itself); so they don't
> fit very well.
I think just allocating a vector is fine. If we get too many we could move
to dynamic allocation of them.
-- Keir
> Thanks,
> -Wei
>
>
next prev parent reply other threads:[~2012-03-23 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 22:03 LWP Interrupt Handler Wei Huang
2012-03-23 22:49 ` Keir Fraser [this message]
2012-03-26 0:08 ` Zhang, Xiantao
2012-03-29 22:54 ` Wei Huang
2012-03-30 8:21 ` Keir Fraser
2012-03-30 19:44 ` Wei Huang
2012-03-30 20:06 ` Keir Fraser
2012-03-30 20:11 ` Wei Huang
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=CB92AE8C.2F427%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=wei.huang2@amd.com \
--cc=xen-devel@lists.xen.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.