@robinsmidsrod I got another board which has two NICs. Net0 is using intel
82567lm, net1 is using intel 82576eb. My patch is on 82576eb. Following are the
results on loopback tests. Enabled debugging level 3 for intel and netdevice.
The failed case shows 1 packet transmitted but nothing received
On 05/02/2016 06:41 PM, Ladi Prosek wrote:
Some of the regions may end up being unmapped, either because
they are optional or because the attempt to map them has failed.
Region types starting at 0 didn't make it easy to test for this
condition.
This commit bumps all valid region types up by 1 wi
On Sat, Apr 30, 2016 at 2:54 PM, Mohammad Oslani
wrote:
> Hello,
>
> We are trying to load windows over ipxe and followed over this page :
> http://ipxe.org/wimboot
>
> However I am unable to get it loaded correctly, after everything is
> loaded and server boots up again I get always a blue scree.
The driver enabled both memory and I/O access even if they were
not usable, e.g. BAR not mapped by BIOS. This commit fixes it by
enabling only the BAR types actually used. The device is also
restored to the original state (in terms of the command PCI
register) on removal.
Reviewed-by: Marcel Apfel
Some of the regions may end up being unmapped, either because
they are optional or because the attempt to map them has failed.
Region types starting at 0 didn't make it easy to test for this
condition.
This commit bumps all valid region types up by 1 with 0 having
the implicit 'unmapped' meaning.
This commit adds two new functions. pci_enable_device gives drivers
finer control over how the PCI device is initialized and
pci_restore_device is the shutdown path counterpart.
adjust_pci_device is now implemented in terms of pci_enable_device
and its functionality hasn't changed, i.e. it still u
This series is a follow-up to our virtio 1.0 discussion. The
first patch adds two new functions as suggested by Michael and
the third one makes virtio-net call them.
Changes v1->v2:
* fixed comment 'busmaster' -> 'bus master'
* renamed functions 'enable_pci_device' -> 'pci_enable_device',
'disa
On 05/02/2016 05:38 PM, Ladi Prosek wrote:
On Mon, May 2, 2016 at 4:21 PM, Marcel Apfelbaum wrote:
On 05/02/2016 04:11 PM, Ladi Prosek wrote:
Some of the regions may end up being unmapped, either because
they are optional or because the attempt to map them has failed.
Region types starting at
On Mon, May 2, 2016 at 4:21 PM, Marcel Apfelbaum wrote:
> On 05/02/2016 04:11 PM, Ladi Prosek wrote:
>>
>> Some of the regions may end up being unmapped, either because
>> they are optional or because the attempt to map them has failed.
>> Region types starting at 0 didn't make it easy to test for
On 05/02/2016 04:11 PM, Ladi Prosek wrote:
Some of the regions may end up being unmapped, either because
they are optional or because the attempt to map them has failed.
Region types starting at 0 didn't make it easy to test for this
condition.
This commit adds VIRTIO_PCI_REGION_NONE with the va
On 05/02/2016 04:11 PM, Ladi Prosek wrote:
The driver enabled both memory and I/O access even if they were
not usable, e.g. BAR not mapped by BIOS. This commit fixes it by
enabling only the BAR types actually used. The device is also
restored to the original state (in terms of the command PCI
reg
On 05/02/2016 04:11 PM, Ladi Prosek wrote:
This commit adds two new functions. pci_enable_device gives drivers
finer control over how the PCI device is initialized and
pci_restore_device is the shutdown path counterpart.
adjust_pci_device is now implemented in terms of pci_enable_device
and its
The driver enabled both memory and I/O access even if they were
not usable, e.g. BAR not mapped by BIOS. This commit fixes it by
enabling only the BAR types actually used. The device is also
restored to the original state (in terms of the command PCI
register) on removal.
Signed-off-by: Ladi Prose
This commit adds two new functions. pci_enable_device gives drivers
finer control over how the PCI device is initialized and
pci_restore_device is the shutdown path counterpart.
adjust_pci_device is now implemented in terms of pci_enable_device
and its functionality hasn't changed, i.e. it still u
Some of the regions may end up being unmapped, either because
they are optional or because the attempt to map them has failed.
Region types starting at 0 didn't make it easy to test for this
condition.
This commit adds VIRTIO_PCI_REGION_NONE with the value of 0
and bumps the valid region types up
This series is a follow-up to our virtio 1.0 discussion. The
first patch adds two new functions as suggested by Michael and
the third one makes virtio-net call them.
Changes v1->v2:
* fixed comment 'busmaster' -> 'bus master'
* renamed functions 'enable_pci_device' -> 'pci_enable_device',
'disa
On Mon, May 02, 2016 at 09:39:34AM +0200, Ladi Prosek wrote:
> On Sun, May 1, 2016 at 2:24 PM, Marcel Apfelbaum wrote:
> > Hi Ladi,
> >
> > On 04/28/2016 06:34 PM, Ladi Prosek wrote:
> >>
> >> adjust_pci_device unconditionally enables both memory and I/O space
> >> access, which may not be necessa
On 05/02/2016 11:00 AM, Ladi Prosek wrote:
On Sun, May 1, 2016 at 2:41 PM, Michael S. Tsirkin wrote:
On Sun, May 01, 2016 at 03:25:07PM +0300, Marcel Apfelbaum wrote:
On 04/28/2016 06:34 PM, Ladi Prosek wrote:
The driver enabled both memory and I/O access even if they were
not usable, e.g. BA
On Mon, May 2, 2016 at 9:58 AM, Marcel Apfelbaum wrote:
> On 05/02/2016 10:39 AM, Ladi Prosek wrote:
>>
>> On Sun, May 1, 2016 at 2:24 PM, Marcel Apfelbaum
>> wrote:
>>>
>>> Hi Ladi,
>>>
>>> On 04/28/2016 06:34 PM, Ladi Prosek wrote:
adjust_pci_device unconditionally enables both m
On Sun, May 1, 2016 at 2:41 PM, Michael S. Tsirkin wrote:
> On Sun, May 01, 2016 at 03:25:07PM +0300, Marcel Apfelbaum wrote:
>> On 04/28/2016 06:34 PM, Ladi Prosek wrote:
>> >The driver enabled both memory and I/O access even if they were
>> >not usable, e.g. BAR not mapped by BIOS. This commit f
On 05/02/2016 10:39 AM, Ladi Prosek wrote:
On Sun, May 1, 2016 at 2:24 PM, Marcel Apfelbaum wrote:
Hi Ladi,
On 04/28/2016 06:34 PM, Ladi Prosek wrote:
adjust_pci_device unconditionally enables both memory and I/O space
access, which may not be necessary.
The above problem is not addressed
On Sun, May 1, 2016 at 2:24 PM, Marcel Apfelbaum wrote:
> Hi Ladi,
>
> On 04/28/2016 06:34 PM, Ladi Prosek wrote:
>>
>> adjust_pci_device unconditionally enables both memory and I/O space
>> access, which may not be necessary.
>
>
> The above problem is not addressed in this patch,
> people my get
@olivernie Thanks for the test feedback. The loopback tests are most of the
time tested with two NICs in the same system, with one being the one under test
and the other one a known working NIC. This ensures that there is no packet
drop in the receive and transmit data paths and that VLAN featur
23 matches
Mail list logo
