From: Tom Goetz <tom.goetz@virtualcomputer.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen: use the trigger info we already have to choose the irq handler
Date: Wed, 25 May 2011 10:33:47 -0400 [thread overview]
Message-ID: <81AA5CC3-B436-468B-9581-9A5EDD80A9B8@virtualcomputer.com> (raw)
In-Reply-To: <20110525142510.GA32231@dumpdata.com>
On May 25, 2011, at 10:25 AM, Konrad Rzeszutek Wilk wrote:
> On Wed, May 25, 2011 at 12:33:23PM +0100, Stefano Stabellini wrote:
>> Do not use pirq_needs_eoi to decide which irq handler to use because Xen
>> always returns true if the guest does not support pirq_eoi_map.
>> Use the trigger information we already have from MP-tables and ACPI.
>>
>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> Reported-by: Thomas Goetz <tcgoetz@gmail.com>
>> Tested-by: Thomas Goetz <tcgoetz@gmail.com>
>
> Tom,
>
> Do you prefer those email addresses or tom.goetz@virtualcomputer.com ?
It doesn't matter to me. I'm signed up to Xen devel with the gmail address because I signed up before we had a domain for the company and never bothered to change it.
> ..
>> - if (pirq_needs_eoi(irq))
>> + if (shareable)
>
> Ok, so for dom0, the sharable flag is determined by the ACPI parsing.. good.
> And for MSI/MSI-X we use xen_bind_pirq_msi_to_irq which sets it to use handle_edge_irq.
>
> The only hazard which you asked me on IRC is for PV guests with Xen PCI front.
> In those cases, we have no idea whether the "GSI" IRQ is edge or level and we
> just assume that anything under 16 is edge. Which is 99% right, except if you
> are to pass in the ACPI IRQ to the guest, or some other weird creature. The MSI/MSI-X
> part of the PCI front are OK too - they use the xen_bind_pirq_msi_to_irq call.
>
> So, putting on the todo list an extension to the PCI PV protocol to pass information
> about the GSI's - whether they are edge or level.
>
> Patch is on the 2.6.40-rc1 train.
prev parent reply other threads:[~2011-05-25 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 11:33 Stefano Stabellini
2011-05-25 14:25 ` Konrad Rzeszutek Wilk
2011-05-25 14:33 ` Tom Goetz [this message]
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=81AA5CC3-B436-468B-9581-9A5EDD80A9B8@virtualcomputer.com \
--to=tom.goetz@virtualcomputer.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.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 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®