All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: Keir Fraser <keir@xen.org>, Xen-devel@lists.xensource.com
Subject: Re: RAM security
Date: Mon, 06 Dec 2010 16:53:33 +0000	[thread overview]
Message-ID: <4CFD150D.6070505@abpni.co.uk> (raw)
In-Reply-To: <C92254B4.153B9%keir@xen.org>


On 06/12/10 16:52, Keir Fraser wrote:
> On 06/12/2010 08:31, "Jonathan Tripathy"<jonnyt@abpni.co.uk>  wrote:
>
>>>> 3) If the physical server was shutdown (e.g. plug pulled), I'm guessing
>>>> this will presetn a problem?
>>> Xen scrubs all memory during boot, unless told not to via a boot parameter.
>>>
>> Now this bit of code makes me happy!
>>
>> Just wondering, if Xen scrubs all memory during boot, why is booting the
>> Hypervisor so fast? My machine has 8GB of RAM and starts nice and snappy..
> It probably takes just a couple of seconds to scrub 8GB. Xen does the
> scrubbing immediately before starting dom0, and you should see it say
> 'Scrubbing RAM...' and extra dots continur to appear until scrubbing is
> complete.
>
>   -- Keir
>
I guess in my head I'm comparing RAM scrubbing to dd if=/dev/zero, which 
takes longer as it's usually to disk

  reply	other threads:[~2010-12-06 16:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46C13AA90DB8844DAB79680243857F0F0AFF44@server1.ABPNI.local>
2010-12-06 14:35 ` RAM security Jonathan Tripathy
2010-12-06 14:49   ` George Dunlap
2010-12-06 15:13     ` Jonathan Tripathy
2010-12-06 15:35     ` Jonathan Tripathy
2010-12-06 16:26       ` Keir Fraser
2010-12-06 16:31         ` Jonathan Tripathy
2010-12-06 16:52           ` Keir Fraser
2010-12-06 16:53             ` Jonathan Tripathy [this message]
2010-12-06 17:05             ` Jan Beulich
2010-12-06 17:12               ` Jonathan Tripathy
2010-12-06 17:17                 ` Jonathan Tripathy

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=4CFD150D.6070505@abpni.co.uk \
    --to=jonnyt@abpni.co.uk \
    --cc=Xen-devel@lists.xensource.com \
    --cc=keir@xen.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.