All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Kai Huang <dev.kai.huang@gmail.com>, Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: Xen crash: map_domain_page() on an NMI path
Date: Fri, 27 Dec 2013 11:38:35 +0000	[thread overview]
Message-ID: <52BD66BB.9040105@citrix.com> (raw)
In-Reply-To: <CAOtp4KrY4OFstNa56NCF61-W9imN4yxDrmKSKBsDgjPDw2qWpQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1652 bytes --]

On 27/12/2013 07:29, Kai Huang wrote:
>
>
>
> On Fri, Dec 20, 2013 at 4:43 PM, Jan Beulich <JBeulich@suse.com
> <mailto:JBeulich@suse.com>> wrote:
>
>     >>> On 19.12.13 at 17:19, Andrew Cooper <andrew.cooper3@citrix.com
>     <mailto:andrew.cooper3@citrix.com>> wrote:
>     > However, for hardware pieces like this which are set up once at the
>     > start of day, and have the hardware pointed at a chosen region,
>     would it
>     > be acceptable to allocate their frames low enough to be covered
>     by the
>     > direct map area (protected by BUG()s?) and set up their base virtual
>     > addresses knowing that there will always be a valid mapping from
>     any Xen
>     > pagetables?  This seems better than constantly playing around
>     with the
>     > mappings.
>
>     That would still require further special casing in map_domain_page().
>
>     In the case here, and with 32-bit no longer a concern, a virtual
>     mapping should rather be obtained at boot time once and for all
>     using vmap().
>
>
> A question about map_domain_page. If I understand correctly, currently
> map_domain_page will still do page table setup with virtual address in
> mapcache area. Why can't we just map all physical memory to XEN's
>  virtual address slot, and do mfn_to_virt to get the virtual address?
>
> -Kai

Xen hands most of the upper canonical half to 64bit PV guest kernels.

The first 5TiB of RAM is unconditionally available via mfn_to_virt, but
Xen supports up to 16TiB of RAM.

Therefore, a server with more than 5TiB of RAM, or with RAM hoplug
regions above the 5TiB boundary require domain mappings to be accessed.

~Andrew

[-- Attachment #1.2: Type: text/html, Size: 3245 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2013-12-27 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 19:37 Xen crash: map_domain_page() on an NMI path Andrew Cooper
2013-12-19 11:00 ` Tim Deegan
2013-12-19 12:11   ` Andrew Cooper
2013-12-19 14:55 ` Jan Beulich
2013-12-19 16:19   ` Andrew Cooper
2013-12-20  8:43     ` Jan Beulich
2013-12-27  7:29       ` Kai Huang
2013-12-27 11:38         ` Andrew Cooper [this message]

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=52BD66BB.9040105@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dev.kai.huang@gmail.com \
    --cc=keir@xen.org \
    --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.