From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: increase evtchn limits
Date: Thu, 20 May 2010 20:41:10 -0700 [thread overview]
Message-ID: <20100520204110.2d421bfe@mantra.us.oracle.com> (raw)
Hi,
I'm trying to boot up with lot more than 32 vcpus on this very large box.
I overcame vcpu_info[MAX_VIRT_CPUS] by doing vcpu placement hypercall
in guest, but now running into evt channel limit (lots of devices):
unsigned long evtchn_pending[sizeof(unsigned long) * 8];
which limits to 512 max for my 64bit dom0. The only recourse seems to
create a new struct shared_info_v2{}, and re-arrange it a bit with lot
more event channels. Since, start_info has magic with version info, I
can just check that in guest and use new shared_info...(doing the design
on the fly here). I can create a new vcpuop saying the guest is using
newer version. Or forget new version of shared_info{}, I can just
put evtchn stuff in my own mfn and tell hypervisor to relocate it,
(just like vcpu_info does) via new VCPUOP_ call.
Keir, what do you think?
thanks,
Mukesh
next reply other threads:[~2010-05-21 3:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 3:41 Mukesh Rathor [this message]
2010-05-21 5:07 ` increase evtchn limits Zhigang Wang
2010-05-21 7:12 ` Keir Fraser
2010-05-21 18:52 ` Mukesh Rathor
2010-05-21 20:15 ` Keir Fraser
2010-05-21 7:01 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2010-05-21 8:14 Jan Beulich
2010-05-21 9:25 ` Keir Fraser
2010-05-21 9:29 ` Keir Fraser
2010-05-21 11:09 ` Jan Beulich
2010-05-21 10:52 ` 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=20100520204110.2d421bfe@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.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;
as well as URLs for NNTP newsgroup(s).