From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] domctl: fix IRQ permission granting/revocation
Date: Wed, 10 Dec 2014 10:12:15 +0000 [thread overview]
Message-ID: <1418206335.19809.49.camel@eu.citrix.com> (raw)
In-Reply-To: <548827E5020000780004E780@mail.emea.novell.com>
On Wed, 2014-12-10 at 10:00 +0000, Jan Beulich wrote:
> >>> On 10.12.14 at 10:53, <Ian.Campbell@eu.citrix.com> wrote:
> > On Wed, 2014-12-10 at 08:07 +0000, Jan Beulich wrote:
> >> Commit 545607eb3c ("x86: fix various issues with handling guest IRQs")
> >> wasn't really consistent in one respect: The granting of access to an
> >> IRQ shouldn't assume the pIRQ->IRQ translation to be the same in both
> >> domains. In fact it is wrong to assume that a translation is already/
> >> still in place at the time access is being granted/revoked.
> >
> > Specifically you need to do the translation using the mapping of the
> > domain doing the granting, not the domain being granted too, correct?
> >
> > It takes a little bit of thought to figure out which domain to check
> > here, it would be worth a sentence or two explaining why this is the
> > right one.
>
> Would
>
> "What is wanted is to translate the incoming pIRQ to an IRQ for
> the invoking domain (as the pIRQ is the only notion the invoking
> domain has of the IRQ), and grant the subject domain access to
> the resulting IRQ."
>
> make this more clear without being purely redundant with the code?
Yes, thanks.
Ian.
next prev parent reply other threads:[~2014-12-10 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 8:07 [PATCH] domctl: fix IRQ permission granting/revocation Jan Beulich
2014-12-10 9:53 ` Ian Campbell
2014-12-10 10:00 ` Jan Beulich
2014-12-10 10:12 ` Ian Campbell [this message]
2014-12-11 11:44 ` Jan Beulich
2014-12-11 17:40 ` Daniel De Graaf
2014-12-10 10:19 ` Julien Grall
2014-12-10 10:46 ` Jan Beulich
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=1418206335.19809.49.camel@eu.citrix.com \
--to=ian.campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.