All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Yuval Shaia <yuval.shaia@oracle.com>,
	bridge <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] [Xen-devel] [PATCH] Add support for netconsole driver used on bridge device with VIF attached
Date: Fri, 03 May 2013 14:36:43 -0000	[thread overview]
Message-ID: <20130503143632.GB3146@phenom.dumpdata.com> (raw)
In-Reply-To: <1367572270.28742.44.camel@zakaz.uk.xensource.com>

On Fri, May 03, 2013 at 10:11:10AM +0100, Ian Campbell wrote:
> On Wed, 2013-05-01 at 12:55 +0100, Yuval Shaia wrote:
> [... snip regurgitation of the thread...]
> > 0001-Add-support-for-netconsole-driver-used-on-bridge-dev.patch
> > 0 2001
> > From: Yuval <yuval.shaia@oracle.com>
> > Date: Tue, 8 Jan 2013 10:08:45 +0200
> > Subject: [PATCH] Add support for netconsole driver used on bridge device with
> >  VIF attached
> 
> Sorry, but this is not what I was asking for.
> 
> Please submit with a coherent changelog based on (i.e. digested from)
> the previous discussion which explains why this change is necessary
> including the background of why it is being made in this way and the
> interaction with the bridging layer. I wasn't asking you to just cut and
> paste that discussion and prepend it to the commit like that.
> 
> The key point is that we don't think that doing netconsole from dom0 to
> a domU on the same host is a useful configuration or something which is
> especially desirable to support but that because of how the bridge
> handles netconsole netback needs to expose this hook in order that
> netconsole can be enabled via a physical device on the same bridge to a
> netserver elsewhere.

I would have thought that doing netconsole on a domU would be a worthwile
attempt - especially to troubleshoot a guest?

> 
> > 
> > Signed-off-by: Yuval <yuval.shaia@oracle.com>
> > ---
> >  drivers/net/xen-netback/interface.c |    8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/drivers/net/xen-netback/interface.c \
> > b/drivers/net/xen-netback/interface.c index 601ae2a..10751f5 100644
> > --- a/drivers/net/xen-netback/interface.c
> > +++ b/drivers/net/xen-netback/interface.c
> > @@ -179,6 +179,13 @@ static u32 xenvif_fix_features(struct net_device *dev, u32 \
> > features)  return features;
> >  }
> >  
> > +static void xenvif_poll_controller(struct net_device *dev)
> > +{
> > +	disable_irq(dev->irq);
> > +	xenvif_interrupt(dev->irq, dev);
> > +	enable_irq(dev->irq);
> > +}
> > +
> >  static const struct xenvif_stat {
> >  	char name[ETH_GSTRING_LEN];
> >  	u16 offset;
> > @@ -237,6 +244,7 @@ static const struct net_device_ops xenvif_netdev_ops = {
> >  	.ndo_stop	= xenvif_close,
> >  	.ndo_change_mtu	= xenvif_change_mtu,
> >  	.ndo_fix_features = xenvif_fix_features,
> > +	.ndo_poll_controller = xenvif_poll_controller,
> >  };
> >  
> >  struct xenvif *xenvif_alloc(struct device *parent, domid_t domid,
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Yuval Shaia <yuval.shaia@oracle.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	bridge <bridge@lists.linux-foundation.org>
Subject: Re: [Xen-devel] [PATCH] Add support for netconsole driver used on bridge device with VIF attached
Date: Fri, 3 May 2013 10:36:32 -0400	[thread overview]
Message-ID: <20130503143632.GB3146@phenom.dumpdata.com> (raw)
In-Reply-To: <1367572270.28742.44.camel@zakaz.uk.xensource.com>

On Fri, May 03, 2013 at 10:11:10AM +0100, Ian Campbell wrote:
> On Wed, 2013-05-01 at 12:55 +0100, Yuval Shaia wrote:
> [... snip regurgitation of the thread...]
> > 0001-Add-support-for-netconsole-driver-used-on-bridge-dev.patch
> > 0 2001
> > From: Yuval <yuval.shaia@oracle.com>
> > Date: Tue, 8 Jan 2013 10:08:45 +0200
> > Subject: [PATCH] Add support for netconsole driver used on bridge device with
> >  VIF attached
> 
> Sorry, but this is not what I was asking for.
> 
> Please submit with a coherent changelog based on (i.e. digested from)
> the previous discussion which explains why this change is necessary
> including the background of why it is being made in this way and the
> interaction with the bridging layer. I wasn't asking you to just cut and
> paste that discussion and prepend it to the commit like that.
> 
> The key point is that we don't think that doing netconsole from dom0 to
> a domU on the same host is a useful configuration or something which is
> especially desirable to support but that because of how the bridge
> handles netconsole netback needs to expose this hook in order that
> netconsole can be enabled via a physical device on the same bridge to a
> netserver elsewhere.

I would have thought that doing netconsole on a domU would be a worthwile
attempt - especially to troubleshoot a guest?

> 
> > 
> > Signed-off-by: Yuval <yuval.shaia@oracle.com>
> > ---
> >  drivers/net/xen-netback/interface.c |    8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/drivers/net/xen-netback/interface.c \
> > b/drivers/net/xen-netback/interface.c index 601ae2a..10751f5 100644
> > --- a/drivers/net/xen-netback/interface.c
> > +++ b/drivers/net/xen-netback/interface.c
> > @@ -179,6 +179,13 @@ static u32 xenvif_fix_features(struct net_device *dev, u32 \
> > features)  return features;
> >  }
> >  
> > +static void xenvif_poll_controller(struct net_device *dev)
> > +{
> > +	disable_irq(dev->irq);
> > +	xenvif_interrupt(dev->irq, dev);
> > +	enable_irq(dev->irq);
> > +}
> > +
> >  static const struct xenvif_stat {
> >  	char name[ETH_GSTRING_LEN];
> >  	u16 offset;
> > @@ -237,6 +244,7 @@ static const struct net_device_ops xenvif_netdev_ops = {
> >  	.ndo_stop	= xenvif_close,
> >  	.ndo_change_mtu	= xenvif_change_mtu,
> >  	.ndo_fix_features = xenvif_fix_features,
> > +	.ndo_poll_controller = xenvif_poll_controller,
> >  };
> >  
> >  struct xenvif *xenvif_alloc(struct device *parent, domid_t domid,
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  reply	other threads:[~2013-05-03 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 11:55 [PATCH] Add support for netconsole driver used on bridge device with VIF attached Yuval Shaia
2013-05-01 11:55 ` [Bridge] " Yuval Shaia
2013-05-03  9:11 ` Ian Campbell
2013-05-03  9:11   ` Ian Campbell
2013-05-03 14:36   ` Konrad Rzeszutek Wilk [this message]
2013-05-03 14:36     ` [Bridge] [Xen-devel] " Konrad Rzeszutek Wilk
2013-05-03 14:43     ` Ian Campbell
2013-05-03 14:43       ` Ian Campbell

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=20130503143632.GB3146@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=yuval.shaia@oracle.com \
    /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.