public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org
Cc: "kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	"Zhang,
	 Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Hollis Blanchard
	<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: RFC/Patch 1/4 portability: split kvm_vm_ioctl v3
Date: Tue, 30 Oct 2007 04:58:22 +0200	[thread overview]
Message-ID: <47269DCE.30203@qumranet.com> (raw)
In-Reply-To: <47260A64.3010309-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>

Carsten Otte wrote:
> Hollis Blanchard wrote:
>> AFAICS, you can just issue two KVM_SET_USER_MEMORY_REGION ioctls in a
>> row, changing 'guest_phys_addr' and leaving 'userspace_addr' the same.
>> That will create an alias.
> That was also my understanding of Avi's comment.

That is indeed what I meant.  It's not 100% identical as aliases dirty 
logging will go to the underlying slot, whereas with two slots mapping 
the same range it's undefined which will get the dirty bits set, but 
userspace can probably handle this easily.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-30  2:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1193668687.7471.5.camel@cotte.boeblingen.de.ibm.com>
     [not found] ` <1193668687.7471.5.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-29 15:08   ` RFC/Patch 1/4 portability: split kvm_vm_ioctl v3 Carsten Otte
     [not found]     ` <1193670516.7471.37.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-29 15:11       ` Izik Eidus
     [not found]         ` <1193670660.4484.26.camel-siXIhNkUrCXckEVJwWePHtCfPAL7FxvL@public.gmane.org>
2007-10-29 15:24           ` Carsten Otte
     [not found]             ` <4725FB3A.1080609-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-29 15:54               ` Hollis Blanchard
2007-10-29 16:29                 ` Carsten Otte
     [not found]                   ` <47260A64.3010309-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-10-29 17:18                     ` Izik Eidus
2007-10-30  2:58                     ` Avi Kivity [this message]
2007-10-29 15:08   ` RFC/Patch 2/4 portability: move memory segmentation to x86.c Carsten Otte
2007-10-29 15:09   ` RFC/Patch 3/4 portability: move get/set_apic_base " Carsten Otte
2007-10-29 15:09   ` RFC/Patch 4/4 portability: move control register helper functions " Carsten Otte

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=47269DCE.30203@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
    --cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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