From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com, Douglas_Warzecha@Dell.com
Subject: Re: [PATCH] linux: force proper address translation in Dell RBU
Date: Thu, 19 Nov 2009 12:22:45 -0500 [thread overview]
Message-ID: <20091119172245.GA9507@phenom.dumpdata.com> (raw)
In-Reply-To: <4B0522FB0200007800020C9D@vpn.id2.novell.com>
On Thu, Nov 19, 2009 at 09:50:35AM +0000, Jan Beulich wrote:
> Replacing virt_to_phys() by virt_to_bus(), and adding code to ensure
> contiguity as required by the firmware.
>
> As usual, written and tested on 2.6.27.37 and made apply to the 2.6.18
> tree without further testing.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> Tested-by: Douglas Warzecha <Douglas_Warzecha@Dell.com>
>
> --- sle11-2009-10-16.orig/drivers/firmware/dell_rbu.c 2009-02-02 09:22:26.000000000 +0100
> +++ sle11-2009-10-16/drivers/firmware/dell_rbu.c 2009-10-26 16:34:16.000000000 +0100
> @@ -169,9 +169,28 @@ static int create_packet(void *data, siz
> spin_lock(&rbu_data.lock);
> goto out_alloc_packet_array;
> }
> +#ifdef CONFIG_XEN
> + if (ordernum && xen_create_contiguous_region(
> + (unsigned long)packet_data_temp_buf, ordernum, 0)) {
> + free_pages((unsigned long)packet_data_temp_buf,
> + ordernum);
> + printk(KERN_WARNING
> + "dell_rbu:%s: failed to adjust new "
> + "packet\n", __func__);
> + retval = -ENOMEM;
> + spin_lock(&rbu_data.lock);
> + goto out_alloc_packet_array;
> + }
> +#endif
I was under the impression we did not want to create any of the #ifdef CONFIG_XEN
at all. As a matter of fact, to actually eliminate or minimize the level of them.
Is there no other way to do this?
next prev parent reply other threads:[~2009-11-19 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 9:50 [PATCH] linux: force proper address translation in Dell RBU Jan Beulich
2009-11-19 10:01 ` Jan Beulich
2009-11-19 17:22 ` Konrad Rzeszutek Wilk [this message]
2009-11-19 17:35 ` Konrad Rzeszutek Wilk
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=20091119172245.GA9507@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Douglas_Warzecha@Dell.com \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.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.