From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [RFC] sanitize memory on system reset
Date: Mon, 17 Jun 2013 09:18:15 +0200 [thread overview]
Message-ID: <51BEB837.4060309@kamp.de> (raw)
In-Reply-To: <51BB1DE4.30403@redhat.com>
Am 14.06.2013 15:43, schrieb Paolo Bonzini:
> Il 14/06/2013 05:44, Alexander Graf ha scritto:
>> Legacy 286 protected mode to real mode switching also happens through
>> the CPU reset PIN, so there certainly is a need to distinguish.
> That's a separate thing because devices aren't reset at all---not just
> memory.
>
> I have pending patches for that, they've been rotting in my tree for a
> while. :)
Which strategy would you follow? Wait until your patches are in or
start with a memory sanitize patch that can be enabled via commandline
Peter
next prev parent reply other threads:[~2013-06-17 7:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 6:09 [Qemu-devel] [RFC] sanitize memory on system reset Peter Lieven
2013-06-13 8:40 ` Stefan Hajnoczi
2013-06-13 8:46 ` Peter Lieven
2013-06-14 11:06 ` Stefan Hajnoczi
2013-06-13 8:51 ` Peter Lieven
2013-06-13 10:55 ` Markus Armbruster
2013-06-13 11:56 ` Anthony Liguori
2013-06-13 12:30 ` Paolo Bonzini
2013-06-14 6:56 ` Christian Borntraeger
2013-06-14 9:44 ` Alexander Graf
2013-06-14 13:43 ` Paolo Bonzini
2013-06-17 7:18 ` Peter Lieven [this message]
2013-06-14 16:14 ` H. Peter Anvin
2013-06-13 14:23 ` Peter Lieven
2013-06-13 15:51 ` Markus Armbruster
2013-06-13 19:20 ` Peter Lieven
2013-06-13 9:22 ` Andreas Färber
2013-06-13 9:33 ` Peter Lieven
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=51BEB837.4060309@kamp.de \
--to=pl@kamp.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=hpa@zytor.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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.