On Thu, Mar 15, 2018 at 12:33 AM, kemi wrote:
> Hi, Jeff
>Today, I deleted the previous kernel images for commit
> 3da90b159b146672f830bcd2489dd3a1f4e9e089
> and commit c0cef30e4ff0dc025f4a1660b8f0ba43ed58426e, respectively. And,
> re-run the same aim7
> jobs for three times for each commit.
Hi, Jeff
Today, I deleted the previous kernel images for commit
3da90b159b146672f830bcd2489dd3a1f4e9e089
and commit c0cef30e4ff0dc025f4a1660b8f0ba43ed58426e, respectively. And, re-run
the same aim7
jobs for three times for each commit. The aim7 score between two commit does
not have obvious
On 2018年02月28日 01:04, Linus Torvalds wrote:
> On Tue, Feb 27, 2018 at 5:43 AM, David Howells wrote:
>> Is it possible there's a stall between the load of RCX and the subsequent
>> instructions because they all have to wait for RCX to become available?
>
> No. Modern Intel big-core CPU's simply
On Tue, Feb 27, 2018 at 5:43 AM, David Howells wrote:
> Is it possible there's a stall between the load of RCX and the subsequent
> instructions because they all have to wait for RCX to become available?
No. Modern Intel big-core CPU's simply aren't that fragile. All these
instructions should do
On Tue, 2018-02-27 at 13:43 +, David Howells wrote:
> Jeff Layton wrote:
>
> >0x813ae828 <+136>: je 0x813ae83a
> >
> >0x813ae82a <+138>: mov0x150(%rbp),%rcx
> >0x813ae831 <+145>: shr%rcx
> >0x813ae834 <+14
Jeff Layton wrote:
>0x813ae828 <+136>: je 0x813ae83a
>0x813ae82a <+138>: mov0x150(%rbp),%rcx
>0x813ae831 <+145>: shr%rcx
>0x813ae834 <+148>: cmp%rcx,0x20(%rax)
>0x813ae838 <+152>: je 0x813ae862
Is i
On Tue, 2018-02-27 at 15:42 +0800, kemi wrote:
>
> On 2018年02月26日 20:33, Jeff Layton wrote:
> > On Mon, 2018-02-26 at 06:43 -0500, Jeff Layton wrote:
> > > On Mon, 2018-02-26 at 16:38 +0800, Ye Xiaolong wrote:
> > > > On 02/25, Jeff Layton wrote:
> > > > > On Sun, 2018-02-25 at 23:05 +0800, kernel
On 2018年02月26日 20:33, Jeff Layton wrote:
> On Mon, 2018-02-26 at 06:43 -0500, Jeff Layton wrote:
>> On Mon, 2018-02-26 at 16:38 +0800, Ye Xiaolong wrote:
>>> On 02/25, Jeff Layton wrote:
On Sun, 2018-02-25 at 23:05 +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a
On Mon, 2018-02-26 at 06:43 -0500, Jeff Layton wrote:
> On Mon, 2018-02-26 at 16:38 +0800, Ye Xiaolong wrote:
> > On 02/25, Jeff Layton wrote:
> > > On Sun, 2018-02-25 at 23:05 +0800, kernel test robot wrote:
> > > > Greeting,
> > > >
> > > > FYI, we noticed a -18.0% regression of aim7.jobs-per-mi
On Mon, 2018-02-26 at 16:38 +0800, Ye Xiaolong wrote:
> On 02/25, Jeff Layton wrote:
> > On Sun, 2018-02-25 at 23:05 +0800, kernel test robot wrote:
> > > Greeting,
> > >
> > > FYI, we noticed a -18.0% regression of aim7.jobs-per-min due to commit:
> > >
> > >
> > > commit: c0cef30e4ff0dc025f4a1
On 02/25, Jeff Layton wrote:
>On Sun, 2018-02-25 at 23:05 +0800, kernel test robot wrote:
>> Greeting,
>>
>> FYI, we noticed a -18.0% regression of aim7.jobs-per-min due to commit:
>>
>>
>> commit: c0cef30e4ff0dc025f4a1660b8f0ba43ed58426e ("iversion: make
>> inode_cmp_iversion{+raw} return bool
On Sun, Feb 25, 2018 at 7:05 AM, kernel test robot
wrote:
>
> FYI, we noticed a -18.0% regression of aim7.jobs-per-min due to commit:
>
> commit: c0cef30e4ff0dc025f4a1660b8f0ba43ed58426e ("iversion: make
> inode_cmp_iversion{+raw} return bool instead of s64")
That looks very unlikely. Can you d
On Sun, 2018-02-25 at 23:05 +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -18.0% regression of aim7.jobs-per-min due to commit:
>
>
> commit: c0cef30e4ff0dc025f4a1660b8f0ba43ed58426e ("iversion: make
> inode_cmp_iversion{+raw} return bool instead of s64")
> https://git.kerne
13 matches
Mail list logo
