On Wed, 6 Jun 2012 16:33:20 -0700, Sean Bruno wrote:
> On Wed, 2012-06-06 at 16:02 -0700, Jung-uk Kim wrote:
> > Buy me a Bulldozer and I'll fix it for you! :-P
>
> Since I have one (FX-8150), do you want me to expose it to the internet
> and let you play with it?
I referred a fairly new use
On Wed, 06 Jun 2012 19:02:16 -0400
Jung-uk Kim wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2012-06-06 17:58:57 -0400, Andriy Gapon wrote:
> > on 31/05/2012 23:28 Jung-uk Kim said the following:
> >> It is simple but I don't like locking scheduler, binding CPU, and
> >> writin
On 06/07/12 11:10, Andriy Gapon wrote:
on 07/06/2012 02:02 Jung-uk Kim said the following:
Any way, hwpstate still isn't quite right even without your patch.
sys/kern/kern_cpu.c cpufreq_curr_sysctl() -> CPUFREQ_SET() ->/* for all
CPU devices */ cf_set_method() ->/* thread_lock(), sched
on 07/06/2012 02:02 Jung-uk Kim said the following:
> Any way, hwpstate still isn't quite right even without your patch.
>
> sys/kern/kern_cpu.c cpufreq_curr_sysctl() -> CPUFREQ_SET() -> /* for all
> CPU devices */ cf_set_method() -> /* thread_lock(), sched_bind(), ... */
> CPUFREQ_DRV_SET()
On Wed, 2012-06-06 at 16:02 -0700, Jung-uk Kim wrote:
> Buy me a Bulldozer and I'll fix it for you! :-P
Since I have one (FX-8150), do you want me to expose it to the internet
and let you play with it?
Sean
___
freebsd-stable@freebsd.org mailing list
h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-06 17:58:57 -0400, Andriy Gapon wrote:
> on 31/05/2012 23:28 Jung-uk Kim said the following:
>> It is simple but I don't like locking scheduler, binding CPU, and
>> writing the same MSR, multiple times for each core.
>
> Not sure if parse t
on 31/05/2012 23:28 Jung-uk Kim said the following:
> It is simple but I don't like locking scheduler, binding CPU, and writing
> the same MSR, multiple times for each core.
Not sure if parse this. The MSR is _written_ /once/ for each core.
(BTW, "locking scheduler" is not a completely accurate d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-05-26 05:34:25 -0400, Andriy Gapon wrote:
> on 26/05/2012 10:02 Yamagi Burmeister said the following:
>> On Fri, 25 May 2012 16:05:56 -0400 Jung-uk Kim
>> wrote:
>>
if we decide so, then I think that we could still keep the
things "
On Sat, 26 May 2012 12:34:25 +0300
Andriy Gapon wrote:
> >>> if we decide so, then I think that we could still keep the things
> >>> "simple". As we currently use the "wholesale" approach (all CPUs are
> >>> set to the same P-state regardless of topology), then we could first
> >>> make a pass o
On Fri, 25 May 2012 16:05:56 -0400
Jung-uk Kim wrote:
> > if we decide so, then I think that we could still keep the things
> > "simple". As we currently use the "wholesale" approach (all CPUs
> > are set to the same P-state regardless of topology), then we could
> > first make a pass of writing
Hi,
I suprised that followings , cited from AMD BKDG(42301 Rev 3.06 - January 25,
2012)
> 2.5.2.1.4
> Core P-state Visibility
> (snip)
> If a compute unit is in a boosted P-state, MSRC001_0063[CurPstate]
> reads back as 0.
^
if in a boosted P-state, MSRC001_0063 "reads back as 0".
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-05-25 15:39:39 -0400, Andriy Gapon wrote:
> on 25/05/2012 20:11 Jung-uk Kim said the following:
>> I just looked through the BKDG and I think you should definitely
>> check MSRC001_0071[18:16]. MSRC001_0063[2:0] is "SharedC" but
>> MSRC001_006
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-05-25 13:11:21 -0400, Jung-uk Kim wrote:
> I just looked through the BKDG and I think you should definitely
> check MSRC001_0071[18:16]. MSRC001_0063[2:0] is "SharedC" but
> MSRC001_0062[2:0] and MSRC001_0071[18:15] are "Not-same-for-all".
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-05-25 11:47:53 -0400, Andriy Gapon wrote:
> on 25/05/2012 17:36 Yamagi Burmeister said the following:
>> Hello, a user at BSDForen.de had the same problem and I helped
>> him to track it down. While I was unable to find a solution I
>> found t
On Fri, 2012-05-18 at 09:18 -0700, Jung-uk Kim wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2012-05-18 01:32:09 -0400, Sean Bruno wrote:
> > Looks like my AMD box isn't quite working correctly with regards
> > to P-states.I noted this repeating periodically: hwpstate0: set
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-05-18 01:32:09 -0400, Sean Bruno wrote:
> Looks like my AMD box isn't quite working correctly with regards
> to P-states.I noted this repeating periodically: hwpstate0: set
> freq failed, err 6
>
>
> I noted these errors when setting the
Looks like my AMD box isn't quite working correctly with regards to
P-states.I noted this repeating periodically:
hwpstate0: set freq failed, err 6
I noted these errors when setting the hwpstate verbose systctl on:
May 17 22:28:32 Alice kernel: hwpstate0: set freq failed, err 6
May 17 22:28:
17 matches
Mail list logo
