mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "SL Baur" <steve@xemacs.org>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "kernel list" <linux-kernel@vger.kernel.org>,
	"Andi Kleen" <andi@firstfloor.org>, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: gart: factor out common code
Date: Wed, 16 Apr 2008 19:55:52 -0700	[thread overview]
Message-ID: <ed10ee420804161955o221539f9p5cbfcc9eaf4b375d@mail.gmail.com> (raw)
In-Reply-To: <20080416081418.GA5105@elf.ucw.cz>

On 4/16/08, Pavel Machek <pavel@ucw.cz> wrote:
> On Tue 2008-04-15 16:25:29, SL Baur wrote:
>  > On 4/15/08, Pavel Machek <pavel@ucw.cz> wrote:

>  > Other reviewer comments:
>  > The casting between struct pci_dev * and u64 is kind of ugly,
>  > I presume the reason for the narrowing casts in the block of
>  > code you moved is documented somewhere.
>
>
> Where am I doing that?

The struct pci_dev */u64 casting is in init_k8_gatt.  If Ingo is happy, then
forget my comment.  I don't have this kind of system to test the patch on, it
was just that as I was looking it over, all the casts kind of made my head
swim.

The narrowing cast is here:
+static inline void enable_gart_translation(struct pci_dev *dev, u64 addr)
+{
+       u32 tmp, ctl;
+
+        /* address of the mappings table */
+        addr >>= 12;
+        tmp = (u32) addr<<4;

Also, putting on my Andrew Morton cap, which I should have done before,
that function is too big to be inlined so you should probably drop the explicit
`inline' and let the compiler decide.

Add a
Reviewed-by: SL Baur <steve@xemacs.org>
if that's appropriate.  I'm satisified that you did a one-for-one code move.

-sb

  reply	other threads:[~2008-04-17  2:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 10:43 Pavel Machek
2008-04-15 23:25 ` SL Baur
2008-04-16  8:14   ` Pavel Machek
2008-04-17  2:55     ` SL Baur [this message]
2008-04-17  6:29       ` Andi Kleen
2008-04-17  7:34         ` SL Baur
2008-04-16 13:08 ` Ingo Molnar
2008-04-16 22:50   ` Yinghai Lu
2008-04-16 22:56     ` Pavel Machek

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=ed10ee420804161955o221539f9p5cbfcc9eaf4b375d@mail.gmail.com \
    --to=steve@xemacs.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®