From: Hollis Blanchard <hollisb@us.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
kvm-ppc <kvm-ppc@vger.kernel.org>, kvm <kvm@vger.kernel.org>
Subject: Re: large page size virtio issues
Date: Wed, 05 Nov 2008 11:31:44 -0600 [thread overview]
Message-ID: <1225906304.26835.75.camel@localhost.localdomain> (raw)
In-Reply-To: <4911D70B.8000905@us.ibm.com>
On Wed, 2008-11-05 at 11:25 -0600, Anthony Liguori wrote:
>
> I think we should just have a VIRTIO_PFN_SHIFT define that is
> architecture specific.
>
> On x86, it'll be 4k. You can make it whatever you want for PPC.
> Fixing all architectures to be 4k is going to suck for architectures
> with < 4k pages.
So we're now in agreement that it should be hardcoded. I don't see much
value in making the actual value arch-specific, but either way it will
solve (at least part of, and maybe all of) my problem. Rusty?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-11-05 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1225836860.15410.32.camel@localhost.localdomain>
[not found] ` <200811052316.47127.rusty@rustcorp.com.au>
[not found] ` <4911A87A.4010209@us.ibm.com>
[not found] ` <4911A87A.4010209-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-11-05 16:32 ` large page size virtio issues Hollis Blanchard
[not found] ` <1225902738.26835.51.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-11-05 17:25 ` Anthony Liguori
2008-11-05 17:31 ` Hollis Blanchard [this message]
[not found] ` <1225906304.26835.75.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-11-05 17:33 ` Anthony Liguori
2008-11-05 17:46 ` Hollis Blanchard
[not found] ` <200811052316.47127.rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
2008-11-05 19:50 ` Hollis Blanchard
2008-11-05 20:08 ` Anthony Liguori
[not found] ` <4911FD32.9050301-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-11-05 20:29 ` Hollis Blanchard
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=1225906304.26835.75.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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