From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ian Campbell <ian.campbell@citrix.com>, Tim Deegan <tim@xen.org>,
Xen-devel <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH for 4.7] xen: Replace alloc_vcpu_guest_context() with vmalloc()
Date: Fri, 21 Aug 2015 19:10:51 +0100 [thread overview]
Message-ID: <55D769AB.2060609@citrix.com> (raw)
In-Reply-To: <20150821175546.GC26425@l.oracle.com>
On 21/08/15 18:55, Konrad Rzeszutek Wilk wrote:
> On Fri, Aug 21, 2015 at 06:51:46PM +0100, Andrew Cooper wrote:
>> This essentially reverts c/s 2037f2adb "x86: introduce
>> alloc_vcpu_guest_context()", including the newer arm bits, but achieves
>> the same end goal by using the newer vmalloc() infrastructure.
> Could you explain what this fixes? Or perhaps with an explanation
> of why this will make Xen [ ]better; [ ] faster [ ] magical.
>
> :-)
Ain't the diffstat enough to qualify for [x]better ;) ?
>
>
> Thanks.
It is relevant to a patch of Rogers which I am reviewing from the no-DM
series. I was writing in reply to that, but this can also do.
alloc_vcpu_guest_context() was introduced long before vmalloc(), and
attempts to make the same end result using per-pcpu fixmap entries,
which scale by the compile-time NR_CPUS.
This patch causes a net reduction in compiled size for each arch (small
for ARM, larger for x86) and removes a scalability limit for compiling
with large numbers of cpus.
I think I can guess what you are going to ask me to do, given this
explanation.
~Andrew
next prev parent reply other threads:[~2015-08-21 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 17:51 [PATCH for 4.7] xen: Replace alloc_vcpu_guest_context() with vmalloc() Andrew Cooper
2015-08-21 17:55 ` Konrad Rzeszutek Wilk
2015-08-21 18:10 ` Andrew Cooper [this message]
2015-08-24 12:19 ` Jan Beulich
2015-08-24 12:19 ` Jan Beulich
2015-08-28 12:41 ` Julien Grall
2015-08-28 12:56 ` Andrew Cooper
2015-08-28 12:57 ` Julien Grall
2015-08-28 13:07 ` Andrew Cooper
2015-08-28 13:13 ` Julien Grall
2015-08-28 13:26 ` 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=55D769AB.2060609@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.