All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Cc: aik@ozlabs.ru, linuxppc-dev@ozlabs.org,
	david@gibson.dropbear.id.au, Adrian Reber <adrian@lisas.de>
Subject: Re: [PATCH v2 2/4] pci: Support 64-bit address translation
Date: Mon, 27 Apr 2015 11:32:29 +0200	[thread overview]
Message-ID: <20150427113229.294bf50d@thh440s> (raw)
In-Reply-To: <1430121753-24818-3-git-send-email-nikunj@linux.vnet.ibm.com>

On Mon, 27 Apr 2015 13:32:31 +0530
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com> wrote:

> Signed-off-by: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
> ---
>  slof/fs/translate.fs | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/slof/fs/translate.fs b/slof/fs/translate.fs
> index e2633e5..9654f24 100644
> --- a/slof/fs/translate.fs
> +++ b/slof/fs/translate.fs
> @@ -33,11 +33,9 @@
>        dup l@ FF AND 0<> ( prop_type address data cfgspace_offset? )
>        3 pick 0= ( prop_type address data cfgspace_offset? reg_prop? )
>        AND NOT IF 
> -         2dup 8 + ( prop_type address data address data' )
> -         2dup l@ 2 pick 8 + l@ + <= -rot l@  >= and  IF
> +         2dup 4 + ( prop_type address data address data' )
> +         2dup @ 2 pick 8 + @ + <= -rot @  >= and  IF
>              l@ 03000000 and 18 rshift nip
> -            \ no 64bit translations supported pretend it is 32bit
> -            dup 3 = IF  1-  THEN
>              ( prop_type type )
>              swap drop ( type )
>              UNLOOP EXIT

Phew, translate-address stuff ... one of my "favorites" ;-)
I wonder whether this will break "legacy" code like board-js2x ...
there might have been a reason for this "pretend it is 32bit" hack
(I've put Adrian Reber on CC:, maybe he still remembers why this was
needed).

Anyway, I think we can fix that up as soon as somebody tries to run the
js2x code again (I still have a YDL PowerStation at home somewhere,
maybe I will have enough spare time to reactivate it one day).

And since your changes itself looks fine to me:

Reviewed-by: Thomas Huth <thuth@redhat.com>

  reply	other threads:[~2015-04-27  9:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  8:02 [PATCH v2 0/4] PCI: Generic fixes and moving enumeration back to QEMU Nikunj A Dadhania
2015-04-27  8:02 ` [PATCH v2 1/4] pci: program correct bridge limit registers during probe Nikunj A Dadhania
2015-04-27  8:17   ` Thomas Huth
2015-04-27  8:02 ` [PATCH v2 2/4] pci: Support 64-bit address translation Nikunj A Dadhania
2015-04-27  9:32   ` Thomas Huth [this message]
2015-04-27  9:57     ` Benjamin Herrenschmidt
2015-04-27 10:12       ` Thomas Huth
2015-04-27  8:02 ` [PATCH v2 3/4] usb: support 64-bit pci bars Nikunj A Dadhania
2015-04-27  8:26   ` Thomas Huth
2015-04-27  8:02 ` [PATCH v2 4/4] pci: Use QEMU created PCI device nodes Nikunj A Dadhania
2015-04-27  8:38   ` Thomas Huth
2015-04-27  9:56     ` Nikunj A Dadhania
2015-04-27 10:14       ` Thomas Huth
2015-04-29  3:12 ` [PATCH v2 0/4] PCI: Generic fixes and moving enumeration back to QEMU Alexey Kardashevskiy
2015-04-29  5:22   ` Nikunj A Dadhania

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=20150427113229.294bf50d@thh440s \
    --to=thuth@redhat.com \
    --cc=adrian@lisas.de \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=nikunj@linux.vnet.ibm.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.