virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Jan Beulich <jbeulich@novell.com>,
	Stephane Eranian <eranian@hpl.hp.com>,
	Ingo Molnar <mingo@elte.hu>,
	"Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Re: [PATCH] Add machine_ops interface  to abstract halting and rebooting
Date: Wed, 28 Mar 2007 12:47:49 -0700	[thread overview]
Message-ID: <460AC665.2090705@goop.org> (raw)
In-Reply-To: <200703282143.53037.ak@suse.de>

Andi Kleen wrote:
> On Wednesday 28 March 2007 21:32, Jeremy Fitzhardinge wrote:
>   
>> machine_ops is an interface for the machine_* functions defined in
>> <linux/reboot.h>.  This is intended to allow hypervisors to intercept
>> the reboot process, but it could be used to implement other x86
>> subarchtecture reboots.
>>     
>
> Both patches added thanks
>   

I presume you've also got the reboot-fixups cleanup patch?

    J

  reply	other threads:[~2007-03-28 19:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 22:13 [PATCH] Simplify smp_call_function*() by using common implementation Jeremy Fitzhardinge
2007-03-27 22:43 ` Randy Dunlap
2007-03-27 22:46   ` Jeremy Fitzhardinge
2007-03-28 19:03 ` Andi Kleen
2007-03-28 19:18   ` Jeremy Fitzhardinge
2007-03-28 19:22     ` Andi Kleen
2007-03-28 19:31       ` [PATCH] Add smp_ops interface Jeremy Fitzhardinge
2007-03-28 19:32       ` [PATCH] Add machine_ops interface to abstract halting and rebooting Jeremy Fitzhardinge
2007-03-28 19:43         ` Andi Kleen
2007-03-28 19:47           ` Jeremy Fitzhardinge [this message]
2007-03-28 19:54             ` Andi Kleen
2007-03-28 20:11               ` [PATCH] Clean up mach_reboot_fixups Jeremy Fitzhardinge
2007-03-28 20:14                 ` Andi Kleen

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=460AC665.2090705@goop.org \
    --to=jeremy@goop.org \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=eranian@hpl.hp.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    --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).