On 31/10/15 19:08, Richard Weinberger wrote:
> Am 31.10.2015 um 17:22 schrieb Anton Ivanov:
>> Richard, can you send me your config.
> Sure. It is basically a defconfig.
I am dragging an old config from some work I did a while back. I will
scrap it and do a defconfig build one I get back home (I
Am 31.10.2015 um 17:22 schrieb Anton Ivanov:
> Richard, can you send me your config.
Sure. It is basically a defconfig.
> I have had it running for a couple of days before submission both under load
> and idle it was doing OK.
Well, what userspace did you try?
I did some more tests, if nanoslee
Am 31.10.2015 um 16:44 schrieb Thomas Meyer:
> Am Samstag, den 31.10.2015, 16:30 +0100 schrieb Richard Weinberger:
>> Am 31.10.2015 um 16:24 schrieb Thomas Meyer:
>>> Am Samstag, den 31.10.2015, 16:21 +0100 schrieb Richard Weinberger:
Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
> mhh. str
Richard, can you send me your config.
I have had it running for a couple of days before submission both under
load and idle it was doing OK.
A
On 31/10/15 15:44, Thomas Meyer wrote:
> Am Samstag, den 31.10.2015, 16:30 +0100 schrieb Richard Weinberger:
>> Am 31.10.2015 um 16:24 schrieb Thomas Me
Am Samstag, den 31.10.2015, 16:30 +0100 schrieb Richard Weinberger:
> Am 31.10.2015 um 16:24 schrieb Thomas Meyer:
> > Am Samstag, den 31.10.2015, 16:21 +0100 schrieb Richard Weinberger:
> > > Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
> > > > mhh. strange. I didn't see this behaviour on my machi
Am 31.10.2015 um 16:24 schrieb Thomas Meyer:
> Am Samstag, den 31.10.2015, 16:21 +0100 schrieb Richard Weinberger:
>> Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
>>> mhh. strange. I didn't see this behaviour on my machine, but my
>>> machine
>>> is a rare single core system so, likely a race condi
Am Samstag, den 31.10.2015, 16:21 +0100 schrieb Richard Weinberger:
> Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
> > mhh. strange. I didn't see this behaviour on my machine, but my
> > machine
> > is a rare single core system so, likely a race condition while
> > relaying
> > the timer interrupt
Am 31.10.2015 um 16:16 schrieb Thomas Meyer:
> mhh. strange. I didn't see this behaviour on my machine, but my machine
> is a rare single core system so, likely a race condition while relaying
> the timer interrupt to the userspace process.
Here I can trigger it by starting UML, logging in and wai
Am Samstag, den 31.10.2015, 16:13 +0100 schrieb Richard Weinberger:
> Am 31.10.2015 um 16:10 schrieb Thomas Meyer:
> > Am Samstag, den 31.10.2015, 14:54 +0100 schrieb Richard Weinberger:
> > > On Thu, Oct 29, 2015 at 7:23 AM, Anton Ivanov
> > > wrote:
> > > > I got the first patchset to build, it
Am 31.10.2015 um 16:10 schrieb Thomas Meyer:
> Am Samstag, den 31.10.2015, 14:54 +0100 schrieb Richard Weinberger:
>> On Thu, Oct 29, 2015 at 7:23 AM, Anton Ivanov
>> wrote:
>>> I got the first patchset to build, it works very well on a single
>>> core
>>> host or with CPU pinning of the UML - the
Am Samstag, den 31.10.2015, 14:54 +0100 schrieb Richard Weinberger:
> On Thu, Oct 29, 2015 at 7:23 AM, Anton Ivanov
> wrote:
> > I got the first patchset to build, it works very well on a single
> > core
> > host or with CPU pinning of the UML - the performance gain is >
> > 25%.
> >
> > However,
On Thu, Oct 29, 2015 at 7:23 AM, Anton Ivanov
wrote:
> I got the first patchset to build, it works very well on a single core
> host or with CPU pinning of the UML - the performance gain is > 25%.
>
> However, I introduced a race somewhere along the way - it crashes UML
> reliably if you do not pi
Am 31.10.2015 4:39 vorm. schrieb Balaco Baco :
>
> > On Fri, Oct 30, 2015 at 7:29 AM, Balaco Baco wrote:
> > >
> > > On Thu, Oct 29, 2015, at 16:55, Richard Weinberger wrote:
> > >> On Thu, Oct 29, 2015 at 8:46 PM, Balaco Baco wrote:
> > >> >> > > >> > Really!? I wish I had read that somewhe
13 matches
Mail list logo
