[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <061C8A8601E8EE4CA8D8FD6990CEA89123BDE6@ORSMSX102.amr.corp.intel.com>
Date: Wed, 8 Feb 2012 18:39:30 +0000
From: "Dave, Tushar N" <tushar.n.dave@...el.com>
To: Michal Kubecek <mkubecek@...e.cz>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"gospo@...hat.com" <gospo@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>,
"jbeulich@...e.com" <jbeulich@...e.com>
Subject: RE: [net-next 02/11] e1000: Adding e1000_dump function
>-----Original Message-----
>From: Michal Kubeček [mailto:mkubecek@...e.cz]
>Sent: Tuesday, February 07, 2012 9:38 AM
>To: netdev@...r.kernel.org
>Cc: Kirsher, Jeffrey T; davem@...emloft.net; Dave, Tushar N;
>gospo@...hat.com; sassmann@...hat.com; jbeulich@...e.com
>Subject: Re: [net-next 02/11] e1000: Adding e1000_dump function
>
>On Tuesday 07 of February 2012 04:33EN, Jeff Kirsher wrote:
>> + if (netif_msg_pktdata(adapter) && buffer_info->dma != 0)
>> + print_hex_dump(KERN_INFO, "", DUMP_PREFIX_ADDRESS,
>> + 16, 1, phys_to_virt(buffer_info->dma),
>> + buffer_info->length, true);
>
>This might cause problems in Xen environment, we encountered a crash in
>e1000e where phys_to_virt() is used the same way. I'm not familiar with
>the details but this is what Jan Beulich wrote about it:
How did you fix the problem in e1000e then? I don't see bus_to_virt used in any of our Ethernet drivers.
Also when running in Xen which arch are you running on?
-Tushar
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists