From: Andi Kleen <ak@suse.de>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, discuss@x86-64.org,
tglx@linutronix.de, torvalds@osdl.org, shai@scalex86.org
Subject: Re: x86_64: 2.6.14-rc4 swiotlb broken
Date: Mon, 17 Oct 2005 17:43:47 +0200 [thread overview]
Message-ID: <200510171743.47926.ak@suse.de> (raw)
In-Reply-To: <20051017153020.GB7652@localhost.localdomain>
On Monday 17 October 2005 17:30, Ravikiran G Thirumalai wrote:
> Yes, I just saw Yasunori-san's patch. Would that be merged for 2.6.14?
I think both are too risky at this point.
> 'Cause 2.6.14 is broken as of now for x86_64 boxes with more than 4G ram.
... that need swiotlb. Which makes that set much much smaller.
Sorry, but your scalex platform is definitely not anywhere release critical
right now.
-Andi
next prev parent reply other threads:[~2005-10-17 15:43 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 9:36 x86_64: 2.6.14-rc4 swiotlb broken Ravikiran G Thirumalai
2005-10-17 9:50 ` Andrew Morton
2005-10-17 9:53 ` Andi Kleen
2005-10-17 10:54 ` Yasunori Goto
2005-10-17 15:27 ` Linus Torvalds
2005-10-17 15:37 ` Ravikiran G Thirumalai
2005-10-17 15:40 ` Andi Kleen
2005-10-17 15:56 ` Muli Ben-Yehuda
2005-10-17 16:02 ` Andi Kleen
2005-10-17 18:53 ` [discuss] " Russell King
2005-10-17 16:02 ` Linus Torvalds
2005-10-17 16:26 ` Andi Kleen
2005-10-17 16:42 ` Linus Torvalds
2005-10-17 17:09 ` Andi Kleen
2005-10-17 17:52 ` Ravikiran G Thirumalai
2005-10-17 18:08 ` [discuss] " Andi Kleen
2005-10-17 18:27 ` Muli Ben-Yehuda
2005-10-17 18:32 ` Andi Kleen
2005-10-17 18:45 ` Muli Ben-Yehuda
2005-10-17 19:04 ` Linus Torvalds
2005-10-17 19:09 ` Andi Kleen
2005-10-17 19:15 ` Arjan van de Ven
2005-10-17 19:47 ` Ravikiran G Thirumalai
2005-10-17 23:50 ` David Lang
2005-10-18 2:29 ` Yasunori Goto
2005-10-18 3:20 ` Ravikiran G Thirumalai
2005-10-18 4:28 ` Yasunori Goto
2005-10-18 6:13 ` Ravikiran G Thirumalai
2005-10-18 10:09 ` Yasunori Goto
2005-10-18 18:51 ` Ravikiran G Thirumalai
2005-10-19 17:18 ` Jon Mason
2005-10-20 7:27 ` Andi Kleen
2005-10-17 18:38 ` Ravikiran G Thirumalai
2005-10-17 18:20 ` Christoph Lameter
2005-10-17 19:04 ` Alex Williamson
2005-10-17 19:26 ` Ravikiran G Thirumalai
2005-10-17 19:52 ` Alex Williamson
2005-10-17 15:30 ` Ravikiran G Thirumalai
2005-10-17 15:43 ` Andi Kleen [this message]
2005-10-17 20:44 ` Andrew Morton
2005-10-17 21:11 ` Linus Torvalds
2005-10-18 0:16 ` Ravikiran G Thirumalai
2005-10-18 8:23 ` Andi Kleen
2005-10-18 19:07 ` [discuss] " Ravikiran G Thirumalai
2005-10-18 15:48 ` Linus Torvalds
2005-10-18 15:50 ` Linus Torvalds
2005-10-18 19:54 ` [discuss] " Ravikiran G Thirumalai
2005-10-18 21:28 ` Alex Williamson
2005-10-18 21:53 ` Ravikiran G Thirumalai
2005-10-18 22:04 ` Alex Williamson
2005-10-18 22:37 ` Alex Williamson
2005-10-18 23:22 ` Ravikiran G Thirumalai
2005-10-19 1:22 ` Alex Williamson
2005-10-19 2:02 ` Alex Williamson
2005-10-19 12:47 ` Yasunori Goto
2005-10-19 14:19 ` Alex Williamson
2005-10-19 18:07 ` Ravikiran G Thirumalai
2005-10-19 20:45 ` Linus Torvalds
2005-10-19 22:52 ` Ravikiran G Thirumalai
2005-10-20 0:51 ` Yasunori Goto
2005-10-20 7:45 ` Andi Kleen
2005-10-18 22:47 ` Ravikiran G Thirumalai
2005-10-17 10:02 ` Muli Ben-Yehuda
2005-10-17 19:07 ` Tony Luck
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=200510171743.47926.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.org \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.org \
/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