LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Chandru <chandru@in.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Alexis Bruemmer <alexisb@us.ibm.com>
Subject: Re: [RFC] [Patch] calgary iommu: Use the first kernel's tce tables in kdump
Date: Mon, 23 Jun 2008 22:29:19 +0300 [thread overview]
Message-ID: <20080623192918.GB6989@il.ibm.com> (raw)
In-Reply-To: <200806211741.43703.chandru@in.ibm.com>
On Sat, Jun 21, 2008 at 05:41:43PM +0530, Chandru wrote:
> kdump kernel fails to boot with calgary iommu and aacraid driver on
> a x366 box. The ongoing dma's of aacraid from the first kernel
> continue to exist until the driver is loaded in the kdump
> kernel. Calgary is initialized prior to aacraid and creation of new
> tce tables causes wrong dma's to occur. Here we try to get the tce
> tables of the first kernel in kdump kernel and use them. While in
> the kdump kernel we do not allocate new tce tables but instead read
> the base address register contents of calgary iommu and use the
> tables that the registers point to. With these changes the kdump
> kernel and hence aacraid now boots normally.
>
> Signed-off-by: Chandru Siddalingappa <chandru@in.ibm.com>
Hi Chandru,
I am not a big fan of this patch, but I guess it would do as a
stop-gap measure. However it is not appropriate for 2.6.26 and should
go in at the beginning of the 2.6.27 merge window. Also, minor
comments below.
> @@ -1206,9 +1213,14 @@ static int __init calgary_init(void)
> struct calgary_bus_info *info;
>
> ret = calgary_locate_bbars();
> +
unneeded whitespace
> @@ -1256,6 +1268,24 @@ error:
> return ret;
> }
>
> +
> +/*
> + * calgary_init_bitmap_from_tce_table():
> + * Funtion for kdump case. In the second/kdump kernel initialize
> + * the bitmap based on the tce table entries obtained from first kernel
> + */
> +static void calgary_init_bitmap_from_tce_table(struct iommu_table *tbl)
> +{
> + u64 *tp;
> + unsigned int index;
> + tp = ((u64 *)tbl->it_base);
> + for (index = 0 ; index < tbl->it_size; index++) {
> + if (*tp != 0x0)
> + set_bit(index, tbl->it_map);
> + tp++;
> + }
I think the code is correct, but the indentation is misleading. Please
fix.
> +}
> +
> static inline int __init determine_tce_table_size(u64 ram)
> {
> int ret;
> @@ -1318,6 +1348,8 @@ static int __init build_detail_arrays(vo
> return 0;
> }
>
> +
> +
unneeded whitespace.
Cheers,
Muli
next prev parent reply other threads:[~2008-06-23 19:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 20:40 chandru
2007-10-09 21:06 ` Muli Ben-Yehuda
2007-10-10 5:30 ` Vivek Goyal
2007-10-14 5:41 ` Muli Ben-Yehuda
2007-10-15 6:29 ` Vivek Goyal
2007-12-24 5:15 ` Chandru
2008-03-10 13:20 ` Chandru
2008-03-10 16:09 ` Andrew Morton
2008-06-21 12:11 ` Chandru
2008-06-21 12:25 ` Mark Salyzyn
2008-06-23 19:29 ` Muli Ben-Yehuda [this message]
2008-07-15 8:45 ` Chandru
2008-07-15 10:52 ` Muli Ben-Yehuda
2008-07-17 23:14 ` Andrew Morton
2008-07-20 9:42 ` Muli Ben-Yehuda
2008-03-11 13:29 ` Vivek Goyal
2008-03-12 5:08 ` Chandru
2008-03-12 9:58 ` Muli Ben-Yehuda
2008-03-12 18:08 ` Vivek Goyal
2008-03-13 15:49 ` Muli Ben-Yehuda
2007-10-10 5:37 ` Vivek Goyal
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=20080623192918.GB6989@il.ibm.com \
--to=muli@il.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alexisb@us.ibm.com \
--cc=chandru@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [RFC] [Patch] calgary iommu: Use the first kernel'\''s tce tables in kdump' \
/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
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).