From: "Joachim Deguara" <joachim.deguara@amd.com>
To: "Pavel Machek" <pavel@suse.cz>
Cc: "shin, jacob" <jacob.shin@amd.com>, "Andi Kleen" <ak@suse.de>,
"Langsdorf, Mark" <mark.langsdorf@amd.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
cpufreq@lists.linux.org.uk
Subject: Re: [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time
Date: Mon, 17 Jul 2006 09:37:10 +0200 [thread overview]
Message-ID: <1153121830.3917.2.camel@lapdog.site> (raw)
In-Reply-To: <20060716015636.GC21162@atrey.karlin.mff.cuni.cz>
On Sun, 2006-07-16 at 03:56 +0200, Pavel Machek wrote:
> > On Thu, 2006-07-13 at 13:06 +0000, Pavel Machek wrote:
> > > Can you run two such tests *in parallel*? That seemed to break it
> > > really quickly.
> > parallel sounds fun, but I don't get it. Two machine or trying to
> go
> > online and offline at the same time? Firestorming two busy parallel
>
> Trying to online and offline at the same time.
>
> > while loops, one turning the core offline and the other online, did
> not
> > bring an oops so I guess this kernel is in the clear in that regard.
>
> Better run two tight loops, each doing online; offline. I got reports
> it crashed machines before, but maybe it is solved.
yeah, that's what I did. Somethings are easier described in bash than in
english. Nothing crashed or oopsed so the green light is there for
online and offline in 2.6.18-rc1 (with my setup).
-joachim
next prev parent reply other threads:[~2006-07-17 7:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:11 [discuss] Re: [PATCH] Allow all Opteron processors to change pstate at same time shin, jacob
2006-07-12 16:14 ` Langsdorf, Mark
2006-07-13 13:06 ` Pavel Machek
2006-07-13 14:32 ` Joachim Deguara
2006-07-16 1:56 ` Pavel Machek
2006-07-17 7:37 ` Joachim Deguara [this message]
2006-07-20 15:59 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 13:37 Bhavana Nagendra
2006-07-06 20:31 Mark Langsdorf
2006-07-07 12:10 ` Andi Kleen
2006-07-07 17:36 ` [discuss] " Langsdorf, Mark
2006-07-10 12:45 ` Joachim Deguara
2006-07-10 13:02 ` Joachim Deguara
2006-07-11 12:55 ` Joachim Deguara
2006-07-11 13:07 ` Andi Kleen
2006-07-11 13:14 ` Arjan van de Ven
2006-07-11 16:15 ` Alan Cox
2006-07-11 16:01 ` Arjan van de Ven
2006-07-11 16:04 ` Andi Kleen
2006-07-11 13:31 ` Langsdorf, Mark
2006-07-11 13:34 ` Arjan van de Ven
2006-07-11 13:51 ` Andi Kleen
2006-07-12 14:06 ` Joachim Deguara
2006-07-12 14:54 ` Andi Kleen
2006-07-25 21:47 ` Langsdorf, Mark
2006-07-26 11:31 ` Joachim Deguara
2006-07-26 16:42 ` Langsdorf, Mark
2006-07-26 16:54 ` Andi Kleen
2006-07-26 18:34 ` Langsdorf, Mark
2006-07-26 18:53 ` Andi Kleen
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=1153121830.3917.2.camel@lapdog.site \
--to=joachim.deguara@amd.com \
--cc=ak@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=discuss@x86-64.org \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=pavel@suse.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