> -----Original Message----- > From: Richard Weinberger [mailto:richard@xxxxxx] > Sent: Tuesday, July 8, 2014 2:40 PM > To: Haiyang Zhang; KY Srinivasan > Cc: devel@xxxxxxxxxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx > Subject: Re: [PATCH] hyperv: Add netpoll support > > Am 08.07.2014 19:55, schrieb Haiyang Zhang: > > > > > >> -----Original Message----- > >> From: Richard Weinberger [mailto:richard@xxxxxx] > >> Sent: Tuesday, July 8, 2014 5:32 AM > >> To: KY Srinivasan; Haiyang Zhang > >> Cc: devel@xxxxxxxxxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; linux- > >> kernel@xxxxxxxxxxxxxxx; Richard Weinberger > >> Subject: [PATCH] hyperv: Add netpoll support > >> > >> In order to have at least a netconsole to debug kernel issues on > >> Windows Azure this patch implements netpoll support. > >> Sending packets is easy, netvsc_start_xmit() does already everything > >> needed. > >> To receive we need to trigger the channel callback which is usally > >> called via tasklet_schedule(). > >> > >> Signed-off-by: Richard Weinberger <richard@xxxxxx> > >> --- > >> drivers/net/hyperv/netvsc_drv.c | 14 ++++++++++++++ > >> 1 file changed, 14 insertions(+) > >> > >> diff --git a/drivers/net/hyperv/netvsc_drv.c > >> b/drivers/net/hyperv/netvsc_drv.c > >> index 4fd71b7..367b71e 100644 > >> --- a/drivers/net/hyperv/netvsc_drv.c > >> +++ b/drivers/net/hyperv/netvsc_drv.c > >> @@ -736,6 +736,17 @@ static int netvsc_set_mac_addr(struct net_device > >> *ndev, void *p) > >> return err; > >> } > >> > >> +#ifdef CONFIG_NET_POLL_CONTROLLER > >> +static void netvsc_poll_controller(struct net_device *net) > >> +{ > >> + struct net_device_context *net_device_ctx = netdev_priv(net); > >> + struct hv_device *dev = net_device_ctx->device_ctx; > >> + > >> + local_bh_disable(); > >> + netvsc_channel_cb(dev->channel); > > > > This can only poll the primary channel not the sub channels. > > Sub channels in terms of one channel per VCPU as KY said? > > *confused*, Since it's used only for debugging, polling the subchannels may not be necessary. Regarding the CPU binding, KY will reply you in another email. Thanks, - Haiyang _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
