netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: linuxppc64-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>,
	netdev@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
	anton@samba.org
Subject: Re: [PATCH] powerpc: ibmveth: Harden driver initilisation for kexec
Date: Fri, 3 Mar 2006 13:11:56 +1100	[thread overview]
Message-ID: <200603031312.00787.michael@ellerman.id.au> (raw)
In-Reply-To: <44079627.6070100@pobox.com>


[-- Attachment #1.1: Type: text/plain, Size: 1464 bytes --]

On Fri, 3 Mar 2006 12:04, Jeff Garzik wrote:
> Santiago Leon wrote:
> > From: Michael Ellerman <michael@ellerman.id.au>
> >
> > After a kexec the veth driver will fail when trying to register with the
> > Hypervisor because the previous kernel has not unregistered.
> >
> > So if the registration fails, we unregister and then try again.
> >
> > Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> > Acked-by: Anton Blanchard <anton@samba.org>
> > Signed-off-by: Santiago Leon <santil@us.ibm.com>
> > ---
> >
> >  drivers/net/ibmveth.c |   32 ++++++++++++++++++++++++++------
> >  1 files changed, 26 insertions(+), 6 deletions(-)
> >
> > Looks good to me, and has been around for a couple of months.
>
> This seems completely bonkers to me:
>
> 	are resources available?
> 	if no
> 		free resources
> 		try again

I'm not sure I follow, are you suggesting we do the h_free_logical_lan() 
unconditionally, followed by h_register_logical_lan() ??

If that's what you mean, I didn't do it that way because it would effect the 
normal code path. This patch only modifies the behaviour if we fail to 
register the adapter. I'm much more comfortable changing the failure case 
than the default.

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

  reply	other threads:[~2006-03-03  2:11 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
2006-03-03  4:12           ` Randy.Dunlap
2006-03-03  1:04     ` Jeff Garzik
2006-03-03  2:11       ` Michael Ellerman [this message]
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=200603031312.00787.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=paulus@samba.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).