From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Tim Deegan (3P)" <Tim.Deegan@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH v2 2/5] arm: implement vcpu_mark_events_pending
Date: Fri, 24 Feb 2012 10:53:02 +0000 [thread overview]
Message-ID: <4F476C0E.2010107@citrix.com> (raw)
In-Reply-To: <1330079609.8557.165.camel@zakaz.uk.xensource.com>
On 24/02/12 10:33, Ian Campbell wrote:
> On Thu, 2012-02-23 at 18:21 +0000, Stefano Stabellini wrote:
>> Implement vcpu_mark_events_pending using the vgic to inject INT 63, that
>> we reserve for Xen usage.
>
> Does this require a trap when the guest acks or EOIs this interrupt?
> What about maintenance interrupts arising from injecting this?
>
> Might we want to instead inject this interrupt as an SGI, so that it
> appears as a per-VCPU interrupt?
I don't think it's possible to register a SGI handler in Linux
currently. The mapping of IRQ numbers to GIC interrupts skips over the
SGIs. This would be easy to fix I think.
David
next prev parent reply other threads:[~2012-02-24 10:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 18:20 [PATCH v2 0/5] xen/arm: event channels and shared_info page Stefano Stabellini
2012-02-23 18:21 ` [PATCH v2 1/5] arm: shared_info page allocation and mapping Stefano Stabellini
2012-02-24 10:22 ` Ian Campbell
2012-02-24 12:46 ` Ian Campbell
2012-02-24 13:04 ` Ian Campbell
2012-02-24 16:50 ` Ian Campbell
2012-02-27 14:19 ` Stefano Stabellini
2012-02-23 18:21 ` [PATCH v2 2/5] arm: implement vcpu_mark_events_pending Stefano Stabellini
2012-02-24 10:33 ` Ian Campbell
2012-02-24 10:53 ` David Vrabel [this message]
2012-02-24 14:15 ` Stefano Stabellini
2012-02-24 17:03 ` Ian Campbell
2012-02-29 17:14 ` Stefano Stabellini
2012-02-23 18:21 ` [PATCH v2 3/5] arm: set the default dom0 max_vcpus value to 1 (currently is 0) Stefano Stabellini
2012-02-24 10:40 ` Ian Campbell
2012-02-24 12:36 ` Stefano Stabellini
2012-02-23 18:21 ` [PATCH v2 4/5] arm: use r12 to pass the hypercall number Stefano Stabellini
2012-02-23 19:29 ` Ian Campbell
2012-02-24 12:21 ` Stefano Stabellini
2012-02-23 18:21 ` [PATCH v2 5/5] arm: introduce more hypercalls Stefano Stabellini
2012-02-24 10:41 ` Ian Campbell
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=4F476C0E.2010107@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Tim.Deegan@citrix.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 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.