From: chen huacai <zltjiangshi@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] Re: bonito: PCI_STATUS questions
Date: Thu, 28 Oct 2010 16:31:33 +0800 [thread overview]
Message-ID: <AANLkTim30+OUqtKD+Kkf7Fx6s+eL66ADHk==h5Ycbz3A@mail.gmail.com> (raw)
In-Reply-To: <20101028045426.GA5599@redhat.com>
Please see bonito64_pcibios_config_access() in
arch/mips/pci/ops-bonito64.c of Linux kernel code.
You will find something useful.
On Thu, Oct 28, 2010 at 12:54 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> On Thu, Oct 28, 2010 at 08:57:01AM +0800, chen huacai wrote:
>> Because the code in PMON and Linux kernel use these bits to verify r/w
>> operations. If one of them is 1 after r/w, PMON and Linux will
>> consider r/w has failed.
>
> Where's that code in Linux?
>
>> I guess that software will not set them to 1, because it is set by
>> hardware when operation fails.
>
> So I guess just making these write 1 to clear according to spec will work?
>
>> On Thu, Oct 28, 2010 at 12:12 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
>> > I see code in bonito.c that clears bits:
>> > PCI_STATUS_REC_MASTER_ABORT | PCI_STATUS_REC_TARGET_ABORT
>> > on each read and write.
>> >
>> > However
>> > 1. I don't see anything in code that would set these bits
>> > 2. The PCI spec says this about the status register:
>> >
>> > Reads to this register behave normally. Writes are slightly different in
>> > that bits can be reset, but not set. A one bit is reset (if it is not
>> > read-only) whenever the register is written, and the write data in the
>> > corresponding bit location is a 1. For instance, to clear bit 14 and not
>> > affect any other bits, write the value 0100_0000_0000_0000b to the
>> > register.
>> >
>> > while the code in bonito.c resets the bits to 0 on each write.
>> >
>> > Comments?
>> >
>> > --
>> > MST
>> >
>>
>>
>>
>> --
>> Huacai Chen
>
--
Huacai Chen
next prev parent reply other threads:[~2010-10-28 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 16:12 [Qemu-devel] bonito: PCI_STATUS questions Michael S. Tsirkin
2010-10-28 0:57 ` [Qemu-devel] " chen huacai
2010-10-28 4:54 ` Michael S. Tsirkin
2010-10-28 8:31 ` chen huacai [this message]
2010-10-29 8:16 ` Michael S. Tsirkin
2010-10-29 13:34 ` chen huacai
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='AANLkTim30+OUqtKD+Kkf7Fx6s+eL66ADHk==h5Ycbz3A@mail.gmail.com' \
--to=zltjiangshi@gmail.com \
--cc=aurelien@aurel32.net \
--cc=mst@redhat.com \
--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).