From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen/x86: actually allocate legacy interrupts on PV guests
Date: Wed, 27 Apr 2016 10:03:20 -0400 [thread overview]
Message-ID: <5720C6A8.7090806@oracle.com> (raw)
In-Reply-To: <5720C14A.1070707@citrix.com>
On 04/27/2016 09:40 AM, David Vrabel wrote:
> On 27/04/16 14:38, Boris Ostrovsky wrote:
>> int xen_nr_legacy_irqs()
>> {
>> if (xen_hvm_domain())
>> return nr_legacy_irqs();
>> if (xen_initial_domain())
>> return NR_IRQS_LEGACY;
>> return 0;
>> }
> Yeah, if that does the right thing...
I think it will break xen_allocate_irq_gsi() again, unless we check for
HVM domain explicitly. Which would be ugly.
-boris
next prev parent reply other threads:[~2016-04-27 14:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 13:15 [PATCH] xen/x86: actually allocate legacy interrupts on PV guests Stefano Stabellini
2016-04-21 9:08 ` Juergen Gross
2016-04-21 9:08 ` Juergen Gross
2016-04-21 9:30 ` Stefano Stabellini
2016-04-21 9:30 ` Stefano Stabellini
2016-04-27 5:02 ` Juergen Gross
2016-04-27 5:02 ` Juergen Gross
2016-04-27 9:35 ` David Vrabel
2016-04-27 9:35 ` [Xen-devel] " David Vrabel
2016-04-27 13:38 ` Boris Ostrovsky
2016-04-27 13:38 ` Boris Ostrovsky
2016-04-27 13:40 ` David Vrabel
2016-04-27 13:40 ` [Xen-devel] " David Vrabel
2016-04-27 14:03 ` Boris Ostrovsky
2016-04-27 14:03 ` Boris Ostrovsky [this message]
2016-05-16 11:23 ` [Xen-devel] " Stefano Stabellini
2016-05-16 13:57 ` Boris Ostrovsky
2016-05-16 15:21 ` Stefano Stabellini
2016-05-16 15:21 ` Stefano Stabellini
2016-05-16 13:57 ` Boris Ostrovsky
2016-05-16 11:23 ` Stefano Stabellini
2016-04-21 11:02 ` [Xen-devel] " Olaf Hering
2016-04-21 11:02 ` Olaf Hering
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=5720C6A8.7090806@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.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.