From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"jeremy@goop.org" <jeremy@goop.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH 4/7] acpi: use indirect call to register gsi in different modes
Date: Thu, 7 Oct 2010 11:41:29 +0100 [thread overview]
Message-ID: <alpine.DEB.2.00.1010071139590.2440@kaball-desktop> (raw)
In-Reply-To: <alpine.LFD.2.00.1010062047340.17015@localhost6.localdomain6>
On Wed, 6 Oct 2010, Thomas Gleixner wrote:
>
>
> On Wed, 6 Oct 2010, H. Peter Anvin wrote:
>
> > On 10/06/2010 10:00 AM, Stefano Stabellini wrote:
> > > Peter,
> > > I sent this patch a while back as part of the "PV on HVM: receive
> > > interrupts as xen events" series (that it is based upon Konrad's
> > > pcifront series, he sent another version to the list yesterday).
> > >
> > > Do you think that this is a reasonble approach?
> > >
> > > If you want to give a look at the whole series you can find it here:
> > >
> > > http://lkml.org/lkml/2010/8/30/170
> > >
> > > everything else is Xen specific stuff.
> > >
> > > Thanks in advance,
> > >
> >
> > On the surface it seems reasonable.
> >
> > Thomas Gleixner has been working on greatly revamping a bunch of the x86
> > interrupt code, and this might interact with his stuff, so it would be
> > good if he could comment on it.
> >
> > [tglx: what they're apparently working on is to redirect APIC interrupts
> > to Xen event channels so they don't have to interact with the simulated
> > memory-mapped APIC. It's "paravirtualization light".]
>
> I'm not touching acpi code. So that should be ok.
In that case would be OK for me to add an acked-by H. Peter Anvin to
this patch?
next prev parent reply other threads:[~2010-10-07 10:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 11:20 [PATCH 0/7] PV on HVM: receive interrupts as xen events Stefano Stabellini
2010-08-30 11:21 ` [PATCH 1/7] xen: support pirq != irq stefano.stabellini
2010-08-30 11:21 ` [PATCH 2/7] xen: get the maximum number of pirqs from xen stefano.stabellini
2010-08-30 11:21 ` [PATCH 3/7] xen: implement xen_hvm_register_pirq stefano.stabellini
2010-08-30 11:21 ` [PATCH 4/7] acpi: use indirect call to register gsi in different modes stefano.stabellini
2010-10-06 17:00 ` Stefano Stabellini
2010-10-06 17:31 ` H. Peter Anvin
2010-10-06 18:48 ` Thomas Gleixner
2010-10-07 10:41 ` Stefano Stabellini [this message]
2010-08-30 11:21 ` [PATCH 5/7] xen: add xen hvm acpi_register_gsi variant stefano.stabellini
2010-08-30 11:21 ` [PATCH 6/7] xen: support GSI -> pirq remapping in PV on HVM guests stefano.stabellini
2010-08-30 11:21 ` [PATCH 7/7] xen: map MSIs into pirqs stefano.stabellini
2010-09-02 19:04 ` [PATCH 0/7] PV on HVM: receive interrupts as xen events Jeremy Fitzhardinge
2010-09-03 13:51 ` Stefano Stabellini
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=alpine.DEB.2.00.1010071139590.2440@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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
all inboxes | Powered by JetHome®