public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jgross@suse.com (Juergen Gross)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] xen/privcmd: add IOCTL_PRIVCMD_MMAP_RESOURCE
Date: Thu, 17 May 2018 08:42:00 +0200	[thread overview]
Message-ID: <69c96876-e5b7-dd6e-8ebe-3493d736e578@suse.com> (raw)
In-Reply-To: <20180509131612.21107-1-paul.durrant@citrix.com>

On 09/05/18 15:16, Paul Durrant wrote:
> My recent Xen patch series introduces a new HYPERVISOR_memory_op to
> support direct priv-mapping of certain guest resources (such as ioreq
> pages, used by emulators) by a tools domain, rather than having to access
> such resources via the guest P2M.
> 
> This patch adds the necessary infrastructure to the privcmd driver and
> Xen MMU code to support direct resource mapping.
> 
> NOTE: The adjustment in the MMU code is partially cosmetic. Xen will now
>       allow a PV tools domain to map guest pages either by GFN or MFN, thus
>       the term 'mfn' has been swapped for 'pfn' in the lower layers of the
>       remap code.
> 
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

Pushed to xen/tip.git for-linus-4.18


Juergen

  parent reply	other threads:[~2018-05-17  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 13:16 [PATCH v5] xen/privcmd: add IOCTL_PRIVCMD_MMAP_RESOURCE Paul Durrant
2018-05-09 13:17 ` Paul Durrant
2018-05-17  6:42 ` Juergen Gross [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-11 12:04 Paul Durrant

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=69c96876-e5b7-dd6e-8ebe-3493d736e578@suse.com \
    --to=jgross@suse.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox