All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>, Tim Deegan <tim@xen.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCHv1] xen: increase default number of PIRQs for hardware domains
Date: Thu, 4 Dec 2014 10:25:26 +0000	[thread overview]
Message-ID: <54803696.5060004@citrix.com> (raw)
In-Reply-To: <20141203203825.GB8802@laptop.dumpdata.com>

On 03/12/14 20:38, Konrad Rzeszutek Wilk wrote:
> On Wed, Dec 03, 2014 at 04:04:20PM +0000, David Vrabel wrote:
>> The default limit for the number of PIRQs for hardware domains (dom0)
>> is not sufficient for some (x86) systems.
>>
>> Since the pirq structures are individually and dynamically allocated,
>> the limit for hardware domains may be increased to the number of
>> possible IRQs.
> 
> Why not also expand the number for the guest?

Because the default doesn't need to be increased for domUs at this time
and I did not want to audit the code to make sure a guest can't (for
example) repeatedly map PIRQs, using up all pirqs/irqs in Xen.

David

  reply	other threads:[~2014-12-04 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 16:04 [PATCHv1] xen: increase default number of PIRQs for hardware domains David Vrabel
2014-12-03 16:08 ` Andrew Cooper
2014-12-03 20:38 ` Konrad Rzeszutek Wilk
2014-12-04 10:25   ` David Vrabel [this message]
2014-12-05  9:44 ` Jan Beulich
2014-12-05 10:28   ` David Vrabel
2014-12-05 12:02   ` Andrew Cooper
2014-12-05 12:19     ` 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=54803696.5060004@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.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.