public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Cyclonus J <cyclonusj@gmail.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Using EPT to map guest MMIO to host MMIO
Date: Fri, 05 Aug 2011 11:08:36 +0200	[thread overview]
Message-ID: <4E3BB314.7030807@siemens.com> (raw)
In-Reply-To: <CAOzbF4eez0XVO6szPh_4f-bHBc_npBBX1eau5xJq+mT8FHhtRg@mail.gmail.com>

On 2011-08-05 10:40, Cyclonus J wrote:
> On Fri, Aug 5, 2011 at 12:41 AM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 2011-08-05 09:20, Cyclonus J wrote:
>>> hi,
>>>
>>> I am wondering if it is possible to map guest MMIO to host MMIO, the
>>> purpose is to reduce VM_EXIT as the page tables will be setup before
>>> MMIO accessing from guest. Here is what I have in mind:
>>
>> This is already the case if you pass through devices AND aligment&size
>> of the MMIO resource allows this.
> 
> I assume here pass through means using VT-d?

...or AMD IOMMU. Yes.

> Unfortunately, I can't
> use it for my case and I need to para-virtualize guest OS as well.

Even with PV, you can't avoid VM exits if the IO access has side
effects, ie. is supposed to trigger some device activity. Or if it is
backed by some logic.

You can only avoid exits if MMIO behaves like RAM. But then it's better
to use RAM directly, like virtio but also real devices do for request data.

Again my question what device you want to optimize precisely.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-08-05  9:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  7:20 Using EPT to map guest MMIO to host MMIO Cyclonus J
2011-08-05  7:41 ` Jan Kiszka
2011-08-05  8:40   ` Cyclonus J
2011-08-05  9:08     ` Jan Kiszka [this message]
2011-08-12  8:05       ` Cyclonus J

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=4E3BB314.7030807@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cyclonusj@gmail.com \
    --cc=kvm@vger.kernel.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