[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: completion timeouts with pin-based interrupts in QEMU hw/nvme
From: |
Klaus Jensen |
Subject: |
Re: completion timeouts with pin-based interrupts in QEMU hw/nvme |
Date: |
Fri, 13 Jan 2023 13:37:50 +0100 |
On Jan 13 12:32, Peter Maydell wrote:
> On Fri, 13 Jan 2023 at 08:55, Klaus Jensen <its@irrelevant.dk> wrote:
> >
> > +CC qemu pci maintainers
> >
> > Michael, Marcel,
> >
> > Do you have any comments on this thread? As you can see one solution is
> > to simply deassert prior to asserting, the other is to reintroduce a
> > pci_irq_pulse(). Both seem to solve the issue.
>
> Both seem to be missing any analysis of "this is what is
> happening, this is where we differ from hardware, this
> is why this is the correct fix". We shouldn't put in
> random "this seems to happen to cause the guest to boot"
> fixes, please.
>
No, I'd like to get to the bottom of this, which is why I'm reaching out
to the pci maintainers to get an idea about if this is a general/known
issue with pin based interrupts on pci.
There are a fair amount of uses of pci_irq_pulse() still left in the
tree.
signature.asc
Description: PGP signature
Re: completion timeouts with pin-based interrupts in QEMU hw/nvme, Klaus Jensen, 2023/01/16
- Re: completion timeouts with pin-based interrupts in QEMU hw/nvme, Keith Busch, 2023/01/16
- Re: completion timeouts with pin-based interrupts in QEMU hw/nvme, Guenter Roeck, 2023/01/17
- Re: completion timeouts with pin-based interrupts in QEMU hw/nvme, Peter Maydell, 2023/01/17
- Re: completion timeouts with pin-based interrupts in QEMU hw/nvme, Guenter Roeck, 2023/01/17
- Re: completion timeouts with pin-based interrupts in QEMU hw/nvme, Peter Maydell, 2023/01/18
- Re: completion timeouts with pin-based interrupts in QEMU hw/nvme, Keith Busch, 2023/01/18