From: David Gibson <dwg@au1.ibm.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, linuxppc-dev@ozlabs.org,
kvm-ppc-devel@lists.sourceforge.net
Subject: Re: [PATCH 2 of 3] [KVM] Add DCR access information to struct kvm_run
Date: Tue, 8 Apr 2008 13:54:41 +1000 [thread overview]
Message-ID: <20080408035441.GA18501@localhost.localdomain> (raw)
In-Reply-To: <200804072225.33040.hollisb@us.ibm.com>
On Mon, Apr 07, 2008 at 10:25:32PM -0500, Hollis Blanchard wrote:
> On Monday 07 April 2008 20:11:28 David Gibson wrote:
> > On Mon, Apr 07, 2008 at 03:53:33PM -0500, Hollis Blanchard wrote:
> > > 1 file changed, 7 insertions(+)
> > > include/linux/kvm.h | 7 +++++++
> > >
> > >
> > > Device Control Registers are essentially another address space found on
> > > PowerPC 4xx processors, analogous to PIO on x86. DCRs are always 32 bits,
> > > and are identified by a 32-bit number.
> >
> > Well... 10-bit, actually.
>
> The mtdcrux description in the ppc440x6 user manual says the following:
>
> Let the contents of register RA denote a Device Control Register.
> The contents of GPR[RS] are placed into the designated Device Control
> Register.
>
> I take that to mean that we must worry about 32 bits worth of DCR numbers.
> Perhaps I should say "no more than" rather than "always".
I think that's less misleading. mtdcrux is very new, anything which
only has the mtdcr instruction certainly can't take DCR numbers above
10 bits, and I would expect that even on chips with mtdcrux the DCR
bus is probably still only 10-bits, although it could be extended.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2008-04-08 3:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 20:53 [PATCH 0 of 3] KVM for PowerPC 440 Hollis Blanchard
2008-04-07 20:53 ` [PATCH 1 of 3] [POWERPC 44x] Export tlb_44x_hwater for KVM Hollis Blanchard
2008-04-10 14:30 ` Josh Boyer
2008-04-07 20:53 ` [PATCH 2 of 3] [KVM] Add DCR access information to struct kvm_run Hollis Blanchard
2008-04-08 1:11 ` David Gibson
2008-04-08 3:25 ` Hollis Blanchard
2008-04-08 3:54 ` David Gibson [this message]
2008-04-08 4:06 ` Hollis Blanchard
2008-04-08 4:16 ` David Gibson
2008-04-10 16:47 ` Josh Boyer
2008-04-07 20:53 ` [PATCH 3 of 3] [KVM POWERPC] PowerPC 440 KVM implementation Hollis Blanchard
2008-04-08 2:12 ` Josh Boyer
2008-04-08 4:00 ` Hollis Blanchard
2008-04-08 2:58 ` Arnd Bergmann
2008-04-08 4:19 ` Hollis Blanchard
2008-04-08 5:09 ` [kvm-ppc-devel] " Arnd Bergmann
2008-04-10 11:55 ` [PATCH 0 of 3] KVM for PowerPC 440 Josh Boyer
2008-04-10 14:26 ` Hollis Blanchard
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=20080408035441.GA18501@localhost.localdomain \
--to=dwg@au1.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.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).