lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYmtgO_E-KKE8zjA04POawJ=4RN3xFUPY__7GF+gSNbNQ@mail.gmail.com>
Date:   Tue, 16 Jul 2019 23:42:15 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     kernel test robot <rong.a.chen@...el.com>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>
Cc:     David Woods <dwoods@...lanox.com>,
        Shravan Kumar Ramani <sramani@...lanox.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        LKP <lkp@...org>
Subject: Re: [gpio] f69e00bd21: unixbench.score -24.2% regression

On Wed, Jul 10, 2019 at 2:15 PM kernel test robot <rong.a.chen@...el.com> wrote:

> FYI, we noticed a -24.2% regression of unixbench.score due to commit:
> commit: f69e00bd21aa6a1961c521b6eb199137fcb8a76a ("gpio: mmio: Support two direction registers")
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master

That's pretty bogus since the test doesn't even seem to be using GPIO.
Further AFAIK Intel chips don't even use that driver.

Can you provide some rootcausing?

If you are using GPIOs from userspace in the test somehow I am
sure both me and Bartosz would be interested to hear how.

Yours,
Linus Walleij

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ