From: Julien Grall <julien.grall@linaro.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] have architectures specify the number of PIRQs a hardware domain gets
Date: Fri, 05 Dec 2014 16:05:47 +0000 [thread overview]
Message-ID: <5481D7DB.3040907@linaro.org> (raw)
In-Reply-To: <5481E05F020000780004D430@mail.emea.novell.com>
On 05/12/14 15:42, Jan Beulich wrote:
>>>> On 05.12.14 at 16:25, <julien.grall@linaro.org> wrote:
>> - XEN_DOMCTL_irq_permission => I don't really understand this bits.
>> AFAIU the pirq number is different on each domain. But we use it to
>> check permission on both domain. Shouldn't we translate the pirq to irq
>> for the current->domain?
>
> Indeed, see also
> http://lists.xenproject.org/archives/html/xen-devel/2014-12/msg00219.html
Do you plan to send a patch to resolve this problem?
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-12-05 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 13:51 [PATCH] have architectures specify the number of PIRQs a hardware domain gets Jan Beulich
2014-12-05 14:27 ` Ian Campbell
2014-12-05 14:36 ` Julien Grall
2014-12-05 14:42 ` Ian Campbell
2014-12-05 15:25 ` Julien Grall
2014-12-05 15:42 ` Jan Beulich
2014-12-05 16:05 ` Julien Grall [this message]
2014-12-05 16:23 ` Jan Beulich
2014-12-05 16:34 ` Stefano Stabellini
2014-12-05 14:48 ` Jan Beulich
2014-12-05 14:51 ` Ian Campbell
2014-12-11 12:07 ` Ian Campbell
2014-12-11 13:16 ` Jan Beulich
2014-12-05 14:48 ` David Vrabel
2014-12-05 14:54 ` 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=5481D7DB.3040907@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--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.