From: <jasper.lowell@bt.com>
To: <balaton@eik.bme.hu>, <mark.cave-ayland@ilande.co.uk>
Cc: jsnow@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/ide: Remove status register read side effect
Date: Thu, 5 Mar 2020 00:47:05 +0000 [thread overview]
Message-ID: <a3eda55a557ea121f7859c3457e64fa92d85de55.camel@bt.com> (raw)
In-Reply-To: <614b7a97-84c2-1861-75d3-51921ae1e4fa@ilande.co.uk>
> Yes, that's correct. However I'm quite confident from booting other
> non-Solaris OSs
> under qemu-system-sparc64 that PCI native mode is being used,
> particularly as it is
> possible to see the related PCI sabre IRQ routing configuration
> changes.
Considering that Solaris 10 is accessing CFR and ARTTIM23 I don't think
there is any doubt that it is using the chip in PCI native mode. I
don't think Solaris 10 even has support for legacy mode.
Thanks,
Jasper Lowell.
On Wed, 2020-03-04 at 21:07 +0000, Mark Cave-Ayland wrote:
> On 04/03/2020 03:11, jasper.lowell@bt.com wrote:
>
> > > cmd646_update_irq() only seems to raise PCI interrupt, should it
> > > also
> > > have
> > > an option to use INT 14 and 15 in legacy mode similar to what my
> > > patch
> > > does for via-ide?
> >
> > Looking through /qemu/hw/ide/cmd646.c it doesn't look like QEMU has
> > support for legacy mode. At the very least, it looks like we
> > default to
> > PCI native mode:
> >
> > static void pci_cmd646_ide_realize(PCIDevice *dev, Error **errp)
> > ...
> > pci_conf[PCI_CLASS_PROG] = 0x8f;
> > ...
> >
> > To add support for legacy mode it would require changing
> > cmd646_update_irq() and maybe cmd646_set_irq() so that interrupts
> > are
> > conditionally raised on IRQ14 and/or IRQ15 when the ports are in
> > legacy
> > mode.
>
> Yes, that's correct. However I'm quite confident from booting other
> non-Solaris OSs
> under qemu-system-sparc64 that PCI native mode is being used,
> particularly as it is
> possible to see the related PCI sabre IRQ routing configuration
> changes.
>
>
> ATB,
>
> Mark.
prev parent reply other threads:[~2020-03-05 0:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 6:50 [PATCH] hw/ide: Remove status register read side effect jasper.lowell
2020-02-21 8:08 ` no-reply
2020-02-21 15:43 ` BALATON Zoltan
2020-02-22 2:07 ` jasper.lowell
2020-02-22 11:47 ` BALATON Zoltan
2020-02-22 17:50 ` BALATON Zoltan
2020-02-22 19:26 ` BALATON Zoltan
2020-02-22 19:32 ` Mark Cave-Ayland
2020-02-22 19:45 ` BALATON Zoltan
2020-02-22 20:05 ` BALATON Zoltan
2020-02-23 7:23 ` jasper.lowell
2020-02-23 15:16 ` BALATON Zoltan
2020-02-25 3:55 ` jasper.lowell
2020-02-25 15:08 ` BALATON Zoltan
2020-02-26 5:22 ` jasper.lowell
2020-02-26 11:07 ` BALATON Zoltan
2020-02-27 5:10 ` jasper.lowell
2020-02-27 5:56 ` jasper.lowell
2020-02-27 11:35 ` BALATON Zoltan
2020-03-04 0:55 ` jasper.lowell
2020-02-27 11:38 ` BALATON Zoltan
2020-03-04 0:58 ` jasper.lowell
2020-03-01 18:02 ` BALATON Zoltan
2020-03-04 3:11 ` jasper.lowell
2020-03-04 8:48 ` BALATON Zoltan
2020-03-04 21:07 ` Mark Cave-Ayland
2020-03-05 0:47 ` jasper.lowell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3eda55a557ea121f7859c3457e64fa92d85de55.camel@bt.com \
--to=jasper.lowell@bt.com \
--cc=balaton@eik.bme.hu \
--cc=jsnow@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).