From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Allen M Kay <allen.m.kay@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Weidong Han <weidong.han@intel.com>,
Dexuan Cui <dexuan.cui@intel.com>
Subject: Re: [PATCH 1/2][VTD] pci mmconfig support to be usedfor ATS
Date: Fri, 21 Nov 2008 10:32:39 +0000 [thread overview]
Message-ID: <49269C57.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C54B7703.1F73B%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 20.11.08 21:20 >>>
>On 20/11/08 20:10, "Kay, Allen M" <allen.m.kay@intel.com> wrote:
>
>>> If this is x86-64 only anyway, why do you need to use fixmap
>>> space for this (and limit things arbitrarily to 4 segments)
>>> rather than using a 256Mb block from one of the unused virtual
>>> address regions in hypervisor space?
>>
>> Can you point me how to use unused virtual address region to do ioremap
>> without using fixmap? Is there a existing code that is already doing this?
>
>Pick yourself a nice piece of virtual address space (see the layout in
>include/asm-x86/config.h -- 0xffff840000000000 would be fine) and then use
>map_pages_to_xen().
While it can be adjusted later anyway, I'd suggest not using a part of this
largest available range - sooner or later we'll want to use this to extend
the 1:1 mapping to 4Tb. Instead, I'd pick another 1Gb range out of the
461Gb reserved region.
Jan
next prev parent reply other threads:[~2008-11-21 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 1:42 [PATCH 1/2][VTD] pci mmconfig support to be used for ATS Kay, Allen M
2008-11-20 8:56 ` Jan Beulich
2008-11-20 20:10 ` Kay, Allen M
2008-11-20 20:20 ` Keir Fraser
2008-11-21 10:32 ` Jan Beulich [this message]
2008-11-20 11:54 ` Espen Skoglund
2008-11-20 20:04 ` Kay, Allen M
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=49269C57.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=allen.m.kay@intel.com \
--cc=dexuan.cui@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=weidong.han@intel.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 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.