I am using Cavium Octeon (CN57XX) guest with QEMU. I want to use qemu
emulated network device e1000. But after booting i am unable to see e1000
in log message or in modules. I am unable to configure networking.
How can i use e1000? Or i have to emulate cavium octeon Ethernet device?
--
Maryyam Mu
Thanks.
Will you be able to point me to the patch which fixes this issue in ixgbevf
driver?
If it is a minor one, I can live with the patch. If possible, point me to
the related file in ixgbevf driver.
In case of updating the driver, only updating ixgbevf alone is enough OR I
need to update both
> -Original Message-
> From: John-Paul Robinson [mailto:j...@uab.edu]
> Sent: Tuesday, February 18, 2014 2:59 PM
> To: Brandeburg, Jesse
> Cc: e1000-devel@lists.sourceforge.net
> Subject: Re: [E1000-devel] questions on ixgbe and 10G performance
> expectations
>
> On 02/17/2014 08:19 PM, Br
On Wed, 2014-02-19 at 00:36 +0100, Christoph Paasch wrote:
> rior to cd14ef54d25 (igb: Change to use statically allocated array for
> MSIx entries), having msix_entries different from NULL was an
> indicator
> that MSIX is enabled.
> In igb_set_interrupt_capabiliy we may fall back to MSI-only. Prio
On Tue, 2014-02-18 at 14:06 +0100, Christoph Paasch wrote:
> When igb_set_interrupt_capability() calls
> igb_reset_interrupt_capability() (e.g., because CONFIG_PCI_MSI is unset),
> num_q_vectors has been set but no vector has yet been allocated.
>
> igb_reset_interrupt_capability() will then call
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org]
> On Behalf Of Christoph Paasch
> Sent: Tuesday, February 18, 2014 3:37 PM
> To: net...@vger.kernel.org; e1000-devel@lists.sourceforge.net
> Cc: David Miller; Kirsher, Jeffrey T; Brandeburg, Jess
Prior to cd14ef54d25 (igb: Change to use statically allocated array for
MSIx entries), having msix_entries different from NULL was an indicator
that MSIX is enabled.
In igb_set_interrupt_capabiliy we may fall back to MSI-only. Prior to
the above patch msix_entries was set to NULL by
igb_reset_inter
From: Christoph Paasch
Date: Tue, 18 Feb 2014 14:06:57 +0100
> When igb_set_interrupt_capability() calls
> igb_reset_interrupt_capability() (e.g., because CONFIG_PCI_MSI is unset),
> num_q_vectors has been set but no vector has yet been allocated.
>
> igb_reset_interrupt_capability() will then c
On 02/17/2014 08:19 PM, Brandeburg, Jesse wrote:
> Forgive my top post.
>
> With the new kernel you may be running into needing faster cleanup to
> increase tx speed. try increasing the interrupt rate via ethtool -C ethX
> rx-usecs 10, yes I said rx because there is only one rate control for th
We currently include in , but I'm about to
remove that from linux/pci.h, so add explicit includes where needed.
Signed-off-by: Bjorn Helgaas
---
drivers/misc/mic/card/mic_device.h |1 +
drivers/misc/mic/host/mic_device.h |1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/misc/
We currently include in , but I'm about to
remove that from linux/pci.h, so add explicit includes where needed.
Signed-off-by: Bjorn Helgaas
---
drivers/misc/mei/hw-me.h |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/misc/mei/hw-me.h b/drivers/misc/mei/hw-me.h
index 80bd829fbd9a
We currently include in , but I'm about to
remove that from linux/pci.h, so add explicit includes where needed.
Signed-off-by: Bjorn Helgaas
---
drivers/iommu/amd_iommu_types.h |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/iommu/amd_iommu_types.h b/drivers/iommu/amd_iommu_types
This is v2 of my rework of part of Stephen's patch [1]. My v1 posting,
with a little discussion, is here [2].
This removes SR-IOV migration support, which seems to be unused.
Changes since v1:
- Drop the removal of MMIO exclusivity.
- Add a few includes of . The SR-IOV migration
support
This reverts commit 74bb1bcc7dbb ("PCI: handle SR-IOV Virtual Function
Migration"), removing this exported interface:
pci_sriov_migration()
Since pci_sriov_migration() is unused, it is impossible to schedule
sriov_migration_task() or use any of the other migration infrastructure.
This is based
From: Amir Vadai
Date: Tue, 18 Feb 2014 14:01:38 +0200
> On 18/02/14 11:11 +0100, Alexander Gordeev wrote:
>> As result of deprecation of MSI-X/MSI enablement functions
>> pci_enable_msix() and pci_enable_msi_block() all drivers
>> using these two interfaces need to be updated to use the
>> new p
From: Alexander Gordeev
Date: Tue, 18 Feb 2014 11:07:52 +0100
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() and pci_enable_msix_range()
>-Original Message-
>From: Vijay Agrawal [mailto:vagra...@ixiacom.com]
>Sent: Sunday, February 16, 2014 10:17 PM
>To: Fujinaka, Todd; e1000-de...@lists.sf.net
>Subject: Re: [E1000-devel] ixgbe-3.17.3 :VLAN tagged packets
>does not work when using PF-PACKET socket ,
>
>Hi Todd,
>
>We are rea
This was an issue in the older versions of ixgbevf. Newer versions should not
show this problem.
Thanks,
Emil
>-Original Message-
>From: Raj Ravi [mailto:mekavi...@gmail.com]
>Sent: Tuesday, February 18, 2014 5:21 AM
>To: e1000-devel@lists.sourceforge.net
>Subject: [E1000-devel] Jumbo fr
The data sheet for our parts is available at intel.com. Just use the search box
and search for "82574 datasheet" and you'll be able to find it.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
From: Nomad Esst [mailto:n
Instead of using -xxx you might try using -vvv instead as that gives you
human readable format.
The dump you provided is only the first 256 bytes. Normally the serial
number is in the extended configuration somewhere at offset 0x140.
Thanks,
Alex
On 02/18/2014 01:00 AM, Nomad Esst wrote:
> Tha
Forgive my top post.
With the new kernel you may be running into needing faster cleanup to increase
tx speed. try increasing the interrupt rate via ethtool -C ethX rx-usecs 10,
yes I said rx because there is only one rate control for the interrupt.
You can easily do line rate tx with 82599. T
Hi,
I am trying to change MTU value to 9000 for a virtual function (SR- IOV
mode).
It works fine when the interface is UP. (using ifconfig mtu 9000 )
But, it fails, If the interface is down. (throwing error message
: RTNETLINK answers: Invalid argument). Note,This error is shown only for
MTU of
When igb_set_interrupt_capability() calls
igb_reset_interrupt_capability() (e.g., because CONFIG_PCI_MSI is unset),
num_q_vectors has been set but no vector has yet been allocated.
igb_reset_interrupt_capability() will then call igb_reset_q_vector,
which assumes that the vector is allocated. As th
On 18/02/14 14:01 +0200, Amir Vadai wrote:
> On 18/02/14 11:11 +0100, Alexander Gordeev wrote:
> > As result of deprecation of MSI-X/MSI enablement functions
> > pci_enable_msix() and pci_enable_msi_block() all drivers
> > using these two interfaces need to be updated to use the
> > new pci_enable_
On 18/02/14 11:11 +0100, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() and pci_enable_msix_range()
> interfaces.
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev
Cc: Jeff Kirsher
Cc: Je
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev
Cc: Jeff Kirsher
Cc: Je
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev
Cc: Jeff Kirsher
Cc: Je
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev
Cc: Jeff Kirsher
Cc: Je
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev
Cc: Jeff Kirsher
Cc: Je
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev
Cc: Jeff Kirsher
Cc: Je
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Cc: e1000-devel@lists.sourceforge.net
Cc: linux-dri...@qlo
Thank you all
The following is the output of lspci -xxx.
0c:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
00: 86 80 d3 10 07 04 18 00 00 00 00 02 10 00 00 00
10: 00 00 de fb 00 00 00 00 01 dc 00 00 00 c0 dd fb
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 00 00
30:
33 matches
Mail list logo
