From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: paravirt_ops.safe_halt vs .halt?
Date: Thu, 21 Sep 2006 12:30:06 -0700 [thread overview]
Message-ID: <4512E83E.80402@goop.org> (raw)
What's paravirt_ops.halt for? Is it the non-safe equivalent to
safe_halt, or is it intended for shutting down the machine? It doesn't
seem to be used anywhere.
J
next reply other threads:[~2006-09-21 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 19:30 Jeremy Fitzhardinge [this message]
2006-09-21 19:44 ` paravirt_ops.safe_halt vs .halt? Chris Wright
2006-09-21 20:32 ` Jeremy Fitzhardinge
2006-09-21 20:58 ` Zachary Amsden
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=4512E83E.80402@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.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 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).