> On 02-Jul-2023, at 2:03 PM, Akihiko Odaki wrote:
>
> The ARI next function number field is undefined for VF. The PF should
> end the linked list formed with the field by specifying 0.
>
> Supersedes: <20230701070133.24877-1-akihiko.od...@daynix.com>
> ("[PATCH 0/4] pci: Compare function
On 2023/07/03 13:52, Michael S. Tsirkin wrote:
On Mon, Jul 03, 2023 at 12:17:16PM +0900, Akihiko Odaki wrote:
On 2023/07/02 21:43, Michael S. Tsirkin wrote:
On Sun, Jul 02, 2023 at 09:02:25PM +0900, Akihiko Odaki wrote:
The ARI next function number field is undefined for VF. The PF should
end
On Mon, Jul 03, 2023 at 12:17:16PM +0900, Akihiko Odaki wrote:
> On 2023/07/02 21:43, Michael S. Tsirkin wrote:
> > On Sun, Jul 02, 2023 at 09:02:25PM +0900, Akihiko Odaki wrote:
> > > The ARI next function number field is undefined for VF. The PF should
> > > end the linked list formed with the
On 2023/07/02 21:43, Michael S. Tsirkin wrote:
On Sun, Jul 02, 2023 at 09:02:25PM +0900, Akihiko Odaki wrote:
The ARI next function number field is undefined for VF. The PF should
end the linked list formed with the field by specifying 0.
Supersedes:
Am 1. Juli 2023 17:46:59 UTC schrieb Olaf Hering :
>According to the 82371FB documentation (82371FB.pdf, 2.3.9. BMIBA—BUS
>MASTER INTERFACE BASE ADDRESS REGISTER, April 1997), the register is
>32bit wide. To properly reset it to default values, all 32bit need to be
>cleared. Bit #0 "Resource
On Sun, Jul 02, 2023 at 08:19:43PM +0900, Akihiko Odaki wrote:
> On 2023/07/02 19:40, Michael S. Tsirkin wrote:
> > On Sun, Jul 02, 2023 at 06:46:25PM +0900, Akihiko Odaki wrote:
> > > The ARI next function number field is undefined for VF so the PF should
> > > end the linked list formed with the
On Sun, Jul 02, 2023 at 09:02:25PM +0900, Akihiko Odaki wrote:
> The ARI next function number field is undefined for VF. The PF should
> end the linked list formed with the field by specifying 0.
>
> Supersedes: <20230701070133.24877-1-akihiko.od...@daynix.com>
> ("[PATCH 0/4] pci: Compare
Currently the only implementers of ARI is SR-IOV devices, and they
behave similar. Share the ARI next function number.
Signed-off-by: Akihiko Odaki
---
docs/pcie_sriov.txt | 4 ++--
include/hw/pci/pcie.h | 2 +-
hw/net/igb.c | 2 +-
hw/net/igbvf.c| 2 +-
hw/nvme/ctrl.c
The current implementers of ARI are all SR-IOV devices. The ARI next
function number field is undefined for VF. The PF should end the linked
list formed with the field by specifying 0.
Fixes: 2503461691 ("pcie: Add some SR/IOV API documentation in
docs/pcie_sriov.txt")
Fixes: 44c2c09488
The ARI next function number field is undefined for VF. The PF should
end the linked list formed with the field by specifying 0.
Supersedes: <20230701070133.24877-1-akihiko.od...@daynix.com>
("[PATCH 0/4] pci: Compare function number and ARI next function number")
V2 -> V3:
Moved the logic to
On 2023/07/02 19:40, Michael S. Tsirkin wrote:
On Sun, Jul 02, 2023 at 06:46:25PM +0900, Akihiko Odaki wrote:
The ARI next function number field is undefined for VF so the PF should
end the linked list formed with the field by specifying 0.
This also changes the value of the field for VF; it
On Sun, Jul 02, 2023 at 06:46:25PM +0900, Akihiko Odaki wrote:
> The ARI next function number field is undefined for VF so the PF should
> end the linked list formed with the field by specifying 0.
>
> This also changes the value of the field for VF; it seems to imply the
> value has some meaning
On Sun, Jul 02, 2023 at 06:49:50PM +0900, Akihiko Odaki wrote:
> On 2023/07/02 18:00, Michael S. Tsirkin wrote:
> > On Sun, Jul 02, 2023 at 05:33:56PM +0900, Akihiko Odaki wrote:
> > > The ARI next function number field is undefined for VF so the PF should
> > > end the linked list formed with the
On Sun, Jul 02, 2023 at 06:46:27PM +0900, Akihiko Odaki wrote:
> The ARI next function number field is undefined for VF so the PF should
> end the linked list formed with the field by specifying 0.
>
> Fixes: 3a977deebe ("Intrdocue igb device emulation")
> Signed-off-by: Akihiko Odaki
> ---
>
On 2023/07/02 18:00, Michael S. Tsirkin wrote:
On Sun, Jul 02, 2023 at 05:33:56PM +0900, Akihiko Odaki wrote:
The ARI next function number field is undefined for VF so the PF should
end the linked list formed with the field by specifying 0.
Fixes: 3a977deebe ("Intrdocue igb device emulation")
The ARI next function number field is undefined for VF. The PF should
end the linked list formed with the field by specifying 0.
Fixes: 44c2c09488 ("hw/nvme: Add support for SR-IOV")
Signed-off-by: Akihiko Odaki
---
hw/nvme/nvme.h| 1 +
hw/core/machine.c | 1 +
hw/nvme/ctrl.c| 3 ++-
3
The ARI next function number field is undefined for VF so the PF should
end the linked list formed with the field by specifying 0.
Fixes: 3a977deebe ("Intrdocue igb device emulation")
Signed-off-by: Akihiko Odaki
---
hw/core/machine.c | 3 ++-
hw/net/igb.c | 5 -
2 files changed, 6
Suggested-by: Michael S. Tsirkin
Signed-off-by: Akihiko Odaki
---
include/hw/pci/pcie.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/hw/pci/pcie.h b/include/hw/pci/pcie.h
index 3cc2b15957..16860e2216 100644
--- a/include/hw/pci/pcie.h
+++ b/include/hw/pci/pcie.h
@@ -134,7
The ARI next function number field is undefined for VF. The PF should
end the linked list formed with the field by specifying 0.
Supersedes: <20230701070133.24877-1-akihiko.od...@daynix.com>
("[PATCH 0/4] pci: Compare function number and ARI next function number")
V1 -> V2:
Fixed migration.
The ARI next function number field is undefined for VF so the PF should
end the linked list formed with the field by specifying 0.
This also changes the value of the field for VF; it seems to imply the
value has some meaning if it differs from one of the PF, but it doesn't.
Fixes: 2503461691
On Sun, Jul 02, 2023 at 05:33:56PM +0900, Akihiko Odaki wrote:
> The ARI next function number field is undefined for VF so the PF should
> end the linked list formed with the field by specifying 0.
>
> Fixes: 3a977deebe ("Intrdocue igb device emulation")
> Signed-off-by: Akihiko Odaki
I would
On Sun, Jul 02, 2023 at 04:55:48AM -0400, Michael S. Tsirkin wrote:
> On Sun, Jul 02, 2023 at 05:46:38PM +0900, Akihiko Odaki wrote:
> > On 2023/07/02 13:58, Michael S. Tsirkin wrote:
> > > On Sat, Jul 01, 2023 at 04:01:22PM +0900, Akihiko Odaki wrote:
> > > > The function number must be lower
On Sun, Jul 02, 2023 at 05:46:38PM +0900, Akihiko Odaki wrote:
> On 2023/07/02 13:58, Michael S. Tsirkin wrote:
> > On Sat, Jul 01, 2023 at 04:01:22PM +0900, Akihiko Odaki wrote:
> > > The function number must be lower than the next function number
> > > advertised with ARI.
> > >
> > >
On 2023/07/02 13:58, Michael S. Tsirkin wrote:
On Sat, Jul 01, 2023 at 04:01:22PM +0900, Akihiko Odaki wrote:
The function number must be lower than the next function number
advertised with ARI.
Signed-off-by: Akihiko Odaki
I don't get this logic at all - where is the limitation coming
On Sun, Jul 02, 2023 at 05:33:53PM +0900, Akihiko Odaki wrote:
> The ARI next function number field is undefined for VF. The PF should
> end the linked list formed with the field by specifying 0.
>
> Supersedes: <20230701070133.24877-1-akihiko.od...@daynix.com>
> ("[PATCH 0/4] pci: Compare
On Sun, Jul 02, 2023 at 05:38:42PM +0900, Akihiko Odaki wrote:
> On 2023/07/02 14:05, Michael S. Tsirkin wrote:
> > On Sat, Jul 01, 2023 at 04:01:21PM +0900, Akihiko Odaki wrote:
> > > The next function numbers are expected to form a linked list ending with
> > > 0.
> > >
> > > Fixes: 3a977deebe
On 2023/07/02 14:05, Michael S. Tsirkin wrote:
On Sat, Jul 01, 2023 at 04:01:21PM +0900, Akihiko Odaki wrote:
The next function numbers are expected to form a linked list ending with
0.
Fixes: 3a977deebe ("Intrdocue igb device emulation")
Signed-off-by: Akihiko Odaki
---
hw/net/igb_core.h |
The ARI next function number field is undefined for VF so the PF should
end the linked list formed with the field by specifying 0.
Fixes: 3a977deebe ("Intrdocue igb device emulation")
Signed-off-by: Akihiko Odaki
---
hw/net/igb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The ARI next function number field is undefined for VF so the PF should
end the linked list formed with the field by specifying 0.
This also changes the value of the field for VF; it seems to imply the
value has some meaning if it differs from one of the PF, but it doesn't.
Fixes: 2503461691
The ARI next function number field is undefined for VF. The PF should
end the linked list formed with the field by specifying 0.
Fixes: 44c2c09488 ("hw/nvme: Add support for SR-IOV")
Signed-off-by: Akihiko Odaki
---
hw/nvme/ctrl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
The ARI next function number field is undefined for VF. The PF should
end the linked list formed with the field by specifying 0.
Supersedes: <20230701070133.24877-1-akihiko.od...@daynix.com>
("[PATCH 0/4] pci: Compare function number and ARI next function number")
Akihiko Odaki (3):
docs: Fix
31 matches
Mail list logo
