From: David Vrabel <david.vrabel@citrix.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: keir@xen.org, george.dunlap@eu.citrix.com,
andrew.cooper3@citrix.com, kexec@lists.infradead.org,
xen-devel@lists.xen.org, ebiederm@xmission.com,
jbeulich@suse.com
Subject: Re: [PATCH] xen/kexec: Clear unused registers before jumping into an image
Date: Fri, 15 Nov 2013 20:07:02 +0000 [thread overview]
Message-ID: <52867EE6.7080205@citrix.com> (raw)
In-Reply-To: <1384530974-26813-1-git-send-email-daniel.kiper@oracle.com>
On 15/11/13 15:56, Daniel Kiper wrote:
> Clear unused registers before jumping into an image. This way
> loaded image could not assume that any register has an specific
> info about earlier running Xen hypervisor. However, it also
> does not mean that the image may expect that a given register
> is zeroed. The image MUST assume that every register has a random
> value or in other words it is uninitialized or has undefined state.
I think this, where the specification (registers undefined) differs from
the implementation (registers zeroed), is the worst option.
I also think it is more likely for an image to inadvertently rely on a
zero value that whatever junk Xen has left behind.
David
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-11-15 20:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 15:56 [PATCH] xen/kexec: Clear unused registers before jumping into an image Daniel Kiper
2013-11-15 20:07 ` David Vrabel [this message]
2013-11-15 21:30 ` Daniel Kiper
2013-11-15 21:30 ` Daniel Kiper
2013-11-18 9:29 ` Jan Beulich
2013-11-18 11:08 ` Daniel Kiper
2013-11-18 11:27 ` Jan Beulich
2013-11-18 11:27 ` Jan Beulich
2013-11-18 11:53 ` Daniel Kiper
2013-11-18 11:53 ` Daniel Kiper
2013-11-18 11:08 ` Daniel Kiper
2013-11-18 11:23 ` David Vrabel
2013-11-18 11:47 ` Daniel Kiper
2013-11-18 12:05 ` George Dunlap
2013-11-18 12:41 ` Daniel Kiper
2013-11-18 12:41 ` Daniel Kiper
2013-11-18 13:13 ` Petr Tesarik
2013-11-18 13:13 ` Petr Tesarik
2013-11-18 14:06 ` George Dunlap
2013-11-19 19:35 ` Konrad Rzeszutek Wilk
2013-11-19 19:35 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-11-19 19:51 ` Konrad Rzeszutek Wilk
2013-11-19 19:51 ` Konrad Rzeszutek Wilk
2013-11-18 14:06 ` George Dunlap
2013-11-18 12:05 ` George Dunlap
2013-11-18 11:47 ` Daniel Kiper
2013-11-18 11:23 ` David Vrabel
2013-11-18 9:29 ` Jan Beulich
2013-11-15 20:07 ` David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2013-11-15 15:56 Daniel Kiper
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=52867EE6.7080205@citrix.com \
--to=david.vrabel@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=ebiederm@xmission.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=kexec@lists.infradead.org \
--cc=xen-devel@lists.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.