All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, Pankaj Gupta <pagupta@redhat.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH] content: reserve device ID for virtio-pmem devices
Date: Tue, 22 May 2018 15:15:41 +0200	[thread overview]
Message-ID: <c2984e27-a8ef-7295-8451-31480ab67216@redhat.com> (raw)
In-Reply-To: <20180522094248.GI21655@stefanha-x1.localdomain>

On 22.05.2018 11:42, Stefan Hajnoczi wrote:
> On Fri, May 18, 2018 at 10:11:06AM +0530, Pankaj Gupta wrote:
>> We need a device ID for virtio-pmem devices. As 24 is already 
>> requested by virtio-mem, so requesting next available(25)
>>
>> Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
>> ---
>>  content.tex | 2 ++
>>  1 file changed, 2 insertions(+)
> 
> virtio-mem is designed for hotplug.  Does it make sense to merge
> virtio-pmem into virtio-mem since you'll need hotplug too?
> 
> Stefan
> 
Hi Stefan,

Initially I had (and even proposed during some discussion) the same
idea. But it turns out that they are fundamentally different.

They are memory devices, yes, but that's the point where they stop being
similar.

While virtio-pmem wants to expose a memory region as persistent memory
and adding a flushing interface, virtio-mem is all about managing
(add/remove/online/offline) sub-chunks and applying protection
mechanisms on the hypervisor side to make sure unplugged memory cannot
(or only in some limited sense) be accessed.

-- 

Thanks,

David / dhildenb

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2018-05-22 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  4:41 [virtio-dev] [PATCH] content: reserve device ID for virtio-pmem devices Pankaj Gupta
2018-05-22  9:42 ` Stefan Hajnoczi
2018-05-22 13:15   ` David Hildenbrand [this message]
2018-05-23  5:01     ` Pankaj Gupta
2018-05-23 10:48       ` Stefan Hajnoczi
2019-03-15 11:00 ` Pankaj Gupta
2019-04-12  5:03 Pankaj Gupta

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=c2984e27-a8ef-7295-8451-31480ab67216@redhat.com \
    --to=david@redhat.com \
    --cc=pagupta@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-dev@lists.oasis-open.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.