From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Patrick Colp <pjcolp@cs.ubc.ca>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: SATA pass-through woes
Date: Mon, 7 Mar 2011 12:36:46 -0500 [thread overview]
Message-ID: <20110307173646.GA4930@dumpdata.com> (raw)
In-Reply-To: <AANLkTikGA9Y4jxTbLFbvsCuy6FoTeu1Q5U2hcf_p7u4u@mail.gmail.com>
On Fri, Mar 04, 2011 at 07:24:24PM -0800, Patrick Colp wrote:
> A quick addendum to this:
>
> I've tried with both PVOPS (2.6.31.13 and 2.6.32.26) and 2.6.18
> kernels. For 2.6.18, the SATA driver doesn't work, so I use the PIIXn
> regular ATA IDE driver (in the BIOS I have the SATA set to export the
> device in IDE mode rather than AHCI, as I don't think I can pass AHCI
> devices through).
And what does your guest config file look like? What does your serial log
look like? What version of Xen are you using (please provide c/s)?Do other
devices on the "failing" machine work with pass-through? What kind of
machine is this? Does it have an IOMMU?
>
> The issue is the same in both (constantly reading in 0xff from the
> status port and SRST failing and eventually giving up).
>
>
> Patrick
>
>
> On 4 March 2011 18:38, Patrick Colp <pjcolp@cs.ubc.ca> wrote:
> > I'm trying to pass my SATA controller through to a domain and have run
> > into a weird situation. I have two machines with the same general
> > class of hardware (Intel PIIX) and the pass-through works on one
> > machine but not the other. On the non-working system, the SATA
> > controller makes port reads, but they don't return the correct values.
> > For example, when running it in dom0, when polling the bmdma status
> > register, it returns 0x60 and when polling the command status register
> > , it returns 0x50. However, when passing it through, the bmdma
> > register returns 0x0 and the command register returns 0xff (the error
> > register also returns 0xff, shedding no additional light on the
> > situation).
> >
> > This is the hardware on the working system:
> >
> > 00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE
> > Controller (rev 01) (prog-if 8f [Master SecP SecO PriP PriO])
> > Subsystem: Intel Corporation Device 544e
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > Stepping- SERR- FastB2B- DisINTx-
> > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> > <TAbort- <MAbort- >SERR- <PERR- INTx-
> > Latency: 0
> > Interrupt: pin B routed to IRQ 19
> > Region 0: I/O ports at 20c8 [size=8]
> > Region 1: I/O ports at 20ec [size=4]
> > Region 2: I/O ports at 20c0 [size=8]
> > Region 3: I/O ports at 20e8 [size=4]
> > Region 4: I/O ports at 20a0 [size=16]
> > Region 5: Memory at d02c4000 (32-bit, non-prefetchable) [size=1K]
> > Capabilities: [70] Power Management version 2
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> > Kernel driver in use: ata_piix
> >
> >
> > This is the hardware on the non-working system:
> >
> > 00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port
> > SATA IDE Controller #1 (prog-if 8f [Master SecP SecO PriP PriO])
> > Subsystem: Dell Device 0293
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > Stepping- SERR- FastB2B- DisINTx-
> > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> > <TAbort- <MAbort- >SERR- <PERR- INTx-
> > Latency: 0
> > Interrupt: pin C routed to IRQ 20
> > Region 0: I/O ports at fe00 [size=8]
> > Region 1: I/O ports at fe10 [size=4]
> > Region 2: I/O ports at fe20 [size=8]
> > Region 3: I/O ports at fe30 [size=4]
> > Region 4: I/O ports at fec0 [size=16]
> > Region 5: I/O ports at ecc0 [size=16]
> > Capabilities: [70] Power Management version 3
> > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> > Capabilities: [b0] PCIe advanced features <?>
> > Kernel driver in use: ata_piix
> >
> >
> > Does anybody have any thoughts about what might be going on here?
> >
> >
> > Patrick
> >
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-03-07 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 2:38 SATA pass-through woes Patrick Colp
2011-03-05 3:24 ` Patrick Colp
2011-03-06 17:42 ` Patrick Colp
2011-03-07 17:36 ` Konrad Rzeszutek Wilk [this message]
2011-03-07 19:43 ` Patrick Colp
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=20110307173646.GA4930@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=pjcolp@cs.ubc.ca \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.