From: John Snow <jsnow@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
philmd@redhat.com, amarkovic@wavecomp.com, mst@redhat.com,
qemu-block@nongnu.org, qemu-devel@nongnu.org, balaton@eik.bme.hu
Subject: Re: [PATCH 0/7] via-ide: fixes and improvements
Date: Tue, 17 Mar 2020 00:22:22 -0400 [thread overview]
Message-ID: <b219c84b-8dc6-e360-85d8-7b0694587750@redhat.com> (raw)
In-Reply-To: <a472d8fb-cff9-66e5-3456-5ff4c670eb32@ilande.co.uk>
On 3/14/20 5:15 AM, Mark Cave-Ayland wrote:
> On 13/03/2020 17:57, John Snow wrote:
>
>> On 3/13/20 4:24 AM, Mark Cave-Ayland wrote:
>>> Following on from the earlier thread "Implement "non 100% native mode"
>>> in via-ide", here is an updated patchset based upon the test cases
>>> sent to me off-list.
>>>
>>> The VIA IDE controller is similar to early versions of the PIIX
>>> controller in that the primary and secondary IDE channels are hardwired
>>> to IRQs 14 and 15 respectively. Guest OSs typically handle this by
>>> either switching the controller to legacy mode, or using native mode and
>>> using a combination of PCI device/vendor ID and/or checking various
>>> registers in PCI configuration space to detect this condition and apply
>>> a special fixed IRQ 14/15 routing.
>>>
>>> This patchset effectively updates the VIA IDE PCI device to follow the
>>> behaviour in the datasheet in two ways: fixing some PCI configuration
>>> space register defaults and behaviours, and always using legacy IRQ 14/15
>>> routing, and once applied allows all our known test images to boot
>>> correctly.
>>>
>>> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>>>
>>>
>>> BALATON Zoltan (2):
>>> ide/via: Get rid of via_ide_init()
>>> pci: Honour wmask when resetting PCI_INTERRUPT_LINE
>>>
>>> Mark Cave-Ayland (5):
>>> via-ide: move registration of VMStateDescription to DeviceClass
>>> via-ide: ensure that PCI_INTERRUPT_LINE is hard-wired to its default
>>> value
>>> via-ide: initialise IDE controller in legacy mode
>>> via-ide: allow guests to write to PCI_CLASS_PROG
>>> via-ide: always use legacy IRQ 14/15 routing
>>>
>>> hw/ide/via.c | 21 +++++----------------
>>> hw/mips/mips_fulong2e.c | 5 ++++-
>>> hw/pci/pci.c | 5 ++++-
>>> include/hw/ide.h | 1 -
>>> 4 files changed, 13 insertions(+), 19 deletions(-)
>>>
>>
>> Does this supersede everything else so far? (Except the two cmd646
>> related series, four patches total, which are already staged)
>
> Yes, that's correct. It passes all our tests, and even better allows the fulong2e CD
> image at the link Zoltan posted to boot.
>
> So I believe it's good unless Alexander has any objections?
>
>
> ATB,
>
> Mark.
>
Tentatively staged! Please let me know during the RC testing phase if
you discover problems.
Thanks, applied to my IDE tree:
https://github.com/jnsnow/qemu/commits/ide
https://github.com/jnsnow/qemu.git
--js
prev parent reply other threads:[~2020-03-17 4:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 8:24 [PATCH 0/7] via-ide: fixes and improvements Mark Cave-Ayland
2020-03-13 8:24 ` [PATCH 1/7] via-ide: move registration of VMStateDescription to DeviceClass Mark Cave-Ayland
2020-03-13 19:50 ` Philippe Mathieu-Daudé
2020-03-13 8:24 ` [PATCH 2/7] ide/via: Get rid of via_ide_init() Mark Cave-Ayland
2020-03-13 8:24 ` [PATCH 3/7] pci: Honour wmask when resetting PCI_INTERRUPT_LINE Mark Cave-Ayland
2020-03-13 8:24 ` [PATCH 4/7] via-ide: ensure that PCI_INTERRUPT_LINE is hard-wired to its default value Mark Cave-Ayland
2020-03-13 8:24 ` [PATCH 5/7] via-ide: initialise IDE controller in legacy mode Mark Cave-Ayland
2020-03-13 8:24 ` [PATCH 6/7] via-ide: allow guests to write to PCI_CLASS_PROG Mark Cave-Ayland
2020-03-13 8:24 ` [PATCH 7/7] via-ide: always use legacy IRQ 14/15 routing Mark Cave-Ayland
2020-03-13 12:12 ` [PATCH 0/7] via-ide: fixes and improvements BALATON Zoltan
2020-03-13 16:34 ` [EXTERNAL][PATCH " Aleksandar Markovic
2020-03-13 17:15 ` BALATON Zoltan
2020-03-13 17:57 ` [PATCH " John Snow
2020-03-13 20:50 ` BALATON Zoltan
2020-03-14 9:15 ` Mark Cave-Ayland
2020-03-17 4:22 ` John Snow [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=b219c84b-8dc6-e360-85d8-7b0694587750@redhat.com \
--to=jsnow@redhat.com \
--cc=amarkovic@wavecomp.com \
--cc=balaton@eik.bme.hu \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--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).