From: Sebastian Sumpf <Sebastian.Sumpf@genode-labs.com>
To: Borislav Petkov <bp@alien8.de>
Cc: tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Bug report] __arch_hweight32/64 x86
Date: Mon, 26 Jun 2023 23:42:51 +0200 [thread overview]
Message-ID: <ce1cc0a5-3393-d16f-eaaf-5e7149d5164f@genode-labs.com> (raw)
In-Reply-To: <20230626210604.GLZJn9vA3gcMAuy/eP@fat_crate.local>
Hello Borislav,
On 6/26/23 23:06, Borislav Petkov wrote:
> Hello,
>
> On Mon, Jun 26, 2023 at 10:49:44PM +0200, Sebastian Sumpf wrote:
>> The 'ALTERNATIVE' macro checks for the popcnt feature. In case this fails
>> the '__sw_hweight' C-function is called from inline assembly with rax and
>> rdi as intput/output operands. However, the code does not contain a clobber
>> list of any callee safe registers that might be touched by the
>> '__sw_height64' C-function.
>> Which registers are those? Can you be more specific?
Registers that are free to use by a called C-function are: rcx, rdx, rsi, rdi,
and r8-r11 for x86_64. See the "System V Application Binary Interface
AMD64 Architecture Processor Supplement" [1] page 21. x86_32 I would have to
look up.
>> Therefore, these registers will not be restored
>> upon function return by the compiler. This leads to varying
>> exceptions/bad behavior caused by the thus corrupted registers later
>> on.
>
> How do I reproduce what you're observing so that I can take a look?
This is hard to tell, I would disable the " X86_FEATURE_POPCNT" feature and use
the ' CONFIG_ARCH_HAS_FAST_MULTIPLIER' option in order to use the multiplier
implementation in '__sw_hweight64' in 'lib/hweight.c' At least that is what
triggered it here.
Regards,
Sebastian
[1] http://www.uclibc.org/docs/psABI-x86_64.pdf
--
Sebastian Sumpf
Genode Labs
http://www.genode-labs.com · http://genode.org
Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
next prev parent reply other threads:[~2023-06-26 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 20:49 Sebastian Sumpf
2023-06-26 21:06 ` Borislav Petkov
2023-06-26 21:42 ` Sebastian Sumpf [this message]
2023-06-26 22:41 ` Dave Hansen
2023-06-27 4:25 ` Borislav Petkov
2023-06-27 16:57 ` Sebastian Sumpf
2023-06-29 9:10 ` David Laight
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=ce1cc0a5-3393-d16f-eaaf-5e7149d5164f@genode-labs.com \
--to=sebastian.sumpf@genode-labs.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®