From: Michael Ellerman <michael@ellerman.id.au>
To: linuxppc64-dev@ozlabs.org
Cc: netdev@vger.kernel.org, "Randy.Dunlap" <rdunlap@xenotime.net>,
jgarzik@pobox.com, anton@samba.org
Subject: Re: [PATCH] powerpc: ibmveth: Harden driver initilisation for kexec
Date: Fri, 3 Mar 2006 12:10:47 +1100 [thread overview]
Message-ID: <200603031210.53220.michael@ellerman.id.au> (raw)
In-Reply-To: <20060302163423.f758c5bc.rdunlap@xenotime.net>
[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]
On Fri, 3 Mar 2006 11:34, Randy.Dunlap wrote:
> On Fri, 3 Mar 2006 11:22:45 +1100 Michael Ellerman wrote:
> > Hi Jeff,
> >
> > I realise it's late, but it'd be really good if you could send this up
> > for 2.6.16, we're hosed without it.
>
> I'm wondering if this means that for every virtual/hypervisor
> situation, we have to modify any $interested_drivers.
> Why wouldn't we come up with a cleaner solution (in the long term)?
>
> E.g., could the hypervisor know when one of it's virtual OSes
> dies or reboots and release its resources then?
It does exactly that for a regular reboot, but when we kexec we _don't_ die or
reboot, as far as the Hypervisor is concerned it's all systems go.
It's something of a double-edged sword, we're totally in control which gives
us lots of flexibility, and _fast_ reboot times, but we also have to do a bit
of extra stuff (ie. this patch) to keep things sane.
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Linuxppc64-dev mailing list
Linuxppc64-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc64-dev
next prev parent reply other threads:[~2006-03-03 1:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060131041055.5623C68A46@ozlabs.org>
[not found] ` <20060131042903.GF28896@krispykreme>
2006-03-02 19:40 ` [PATCH] powerpc: ibmveth: Harden driver initilisation for kexec Santiago Leon
2006-03-03 0:22 ` Michael Ellerman
2006-03-03 0:34 ` Randy.Dunlap
2006-03-03 1:00 ` Paul Mackerras
2006-03-03 1:10 ` Michael Ellerman [this message]
2006-03-03 4:12 ` Randy.Dunlap
2006-03-03 1:04 ` Jeff Garzik
2006-03-03 2:11 ` Michael Ellerman
2006-03-27 1:11 ` Michael Ellerman
2006-04-26 10:37 ` Michael Ellerman
2006-04-28 19:51 ` Santiago Leon
2006-08-29 12:58 ` Michael Ellerman
2006-09-18 4:31 Michael Ellerman
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=200603031210.53220.michael@ellerman.id.au \
--to=michael@ellerman.id.au \
--cc=anton@samba.org \
--cc=jgarzik@pobox.com \
--cc=linuxppc64-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).