qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Fam Zheng <fam.zheng@bytedance.com>, qemu-devel@nongnu.org
Cc: "Eduardo Habkost" <eduardo@habkost.net>,
	"Peter Xu" <peterx@redhat.com>,
	fam@euphon.net, "Igor Mammedov" <imammedo@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Eric Blake" <eblake@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	stefanha@redhat.com
Subject: Re: [PATCH] hostmem: Add clear option to file backend
Date: Thu, 2 Mar 2023 12:31:46 +0100	[thread overview]
Message-ID: <377c3521-ffe1-074b-48ac-71fd445b3bb4@redhat.com> (raw)
In-Reply-To: <20230302110925.4680-1-fam.zheng@bytedance.com>

On 02.03.23 12:09, Fam Zheng wrote:
> This adds a memset to clear the backing memory. This is useful in the
> case of PMEM DAX to drop dirty data, if the backing memory is handed
> over from a previous application or firmware which didn't clean up
> before exiting.
> 

Why can't the VM manager do that instead? If you have a file that's 
certainly easily possible.

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2023-03-02 11:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 11:09 [PATCH] hostmem: Add clear option to file backend Fam Zheng
2023-03-02 11:31 ` David Hildenbrand [this message]
2023-03-02 11:37   ` [External] " Feiran Zheng
2023-03-02 11:39     ` David Hildenbrand
2023-03-02 11:48       ` Feiran Zheng
2023-03-02 11:54         ` David Hildenbrand
2023-03-02 13:31           ` Feiran Zheng
2023-03-02 11:44   ` Daniel P. Berrangé
2023-03-02 11:57     ` [External] " Feiran Zheng
2023-03-02 13:56       ` David Hildenbrand
2023-03-02 14:26         ` David Hildenbrand
2023-03-02 16:14         ` Stefan Hajnoczi

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=377c3521-ffe1-074b-48ac-71fd445b3bb4@redhat.com \
    --to=david@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=fam.zheng@bytedance.com \
    --cc=fam@euphon.net \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).