public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 1/2] KVM: Document KVM_SET_USER_MEMORY_REGION
Date: Thu, 25 Mar 2010 13:58:40 +0200	[thread overview]
Message-ID: <4BAB4FF0.5060106@redhat.com> (raw)
In-Reply-To: <310EF8EB-9271-4375-BB51-9FDBFD2F6576@suse.de>

On 03/25/2010 01:54 PM, Alexander Graf wrote:
>
> Am 25.03.2010 um 12:49 schrieb Avi Kivity <avi@redhat.com>:
>
>> On 03/25/2010 01:10 PM, Alexander Graf wrote:
>>>
>>> Am 25.03.2010 um 11:31 schrieb Avi Kivity <avi@redhat.com>:
>>>
>>>>
>>>> +It is recommended to use this API instead of the 
>>>> KVM_SET_MEMORY_REGION ioctl.
>>>
>>> Why? What's wrong with SET_MEM_REGION?
>>>
>>
>> It doesn't allow any control over the memory.  So it found its way 
>> into Documentation/feature-removal-schedule.txt.
>
> Definitely worth adding to the above phrase then.
>

Will do.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-03-25 11:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 10:31 [PATCH 0/2] Document KVM_SET_USER_MEMORY_REGION and KVM_SET_TSS_ADDR Avi Kivity
2010-03-25 10:31 ` [PATCH 1/2] KVM: Document KVM_SET_USER_MEMORY_REGION Avi Kivity
2010-03-25 10:34   ` Pekka Enberg
2010-03-25 11:10   ` Alexander Graf
2010-03-25 11:49     ` Avi Kivity
2010-03-25 11:54       ` Alexander Graf
2010-03-25 11:58         ` Avi Kivity [this message]
2010-03-25 10:31 ` [PATCH 2/2] KVM: Document KVM_SET_TSS_ADDR Avi Kivity
2010-03-25 10:36   ` Pekka Enberg
2010-03-25 10:43     ` Avi Kivity
2010-03-25 12:00       ` Pekka Enberg
2010-03-25 12:02         ` Avi Kivity

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=4BAB4FF0.5060106@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=penberg@cs.helsinki.fi \
    /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