public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Doug Warzecha <Douglas_Warzecha@dell.com>
Cc: abhay_salunke@dell.com, matt_domsch@dell.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.12-rc6] char: Add Dell Systems Management Base driver
Date: Thu, 16 Jun 2005 19:59:29 +0200	[thread overview]
Message-ID: <m1fyvinpxa.fsf@muc.de> (raw)
In-Reply-To: <20050616173024.GA2596@sysman-doug.us.dell.com> (Doug Warzecha's message of "Thu, 16 Jun 2005 12:30:24 -0500")

Doug Warzecha <Douglas_Warzecha@dell.com> writes:

> +static void *tvm_alloc_suitable(unsigned long size, unsigned long phys_max)
> +{
> +	void *ptr;
> +	unsigned int flags = GFP_KERNEL;
> +
> +	while ((ptr = kmalloc(size, flags)) != NULL) {
> +		if ((virt_to_phys(ptr) + size - 1) <= phys_max)
> +			break;
> +
> +		kfree(ptr);
> +		ptr = NULL;
> +
> +		if (flags & GFP_DMA)
> +			break;
> +		flags |= GFP_DMA;
> +	}
> +	return ptr;

Umm - what's that? 

Please drop that immediately. 2.6.13 will hopefully have GFP_DMA32
on x86-64 that will make it fully obsolete.

And even before that you can use pci_alloc_consistent() - that
will do the right now and later.

... haven't read on.

But there seems to be a use of register_ioctl32_conversion. That
needs to be replaced with ->compat_ioctl, since the former
will soon go.

-Andi

  reply	other threads:[~2005-06-16 18:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 17:30 [PATCH 2.6.12-rc6] char: Add Dell Systems Management Base driver Doug Warzecha
2005-06-16 17:59 ` Andi Kleen [this message]
2005-06-16 18:28 ` Brian Gerst
2005-06-16 21:20 ` Alexey Dobriyan
2005-06-16 22:04 ` Chris Wedgwood
2005-06-17  4:30 ` Andrey Panin
2005-06-20  9:56 ` Pavel Machek
2005-06-25  1:31 ` Chris Wedgwood

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=m1fyvinpxa.fsf@muc.de \
    --to=ak@muc.de \
    --cc=Douglas_Warzecha@dell.com \
    --cc=abhay_salunke@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt_domsch@dell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox