From: Kanna Scarlet <knscarlet@gnuweeb.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Cc: Kanna Scarlet <knscarlet@gnuweeb.org>,
Ard Biesheuvel <ardb@kernel.org>,
Bill Metzenthen <billm@melbpc.org.au>,
Brijesh Singh <brijesh.singh@amd.com>,
Joerg Roedel <jroedel@suse.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Michael Roth <michael.roth@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
Sean Christopherson <seanjc@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ammar Faizi <ammarfaizi2@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/1] x86 change mov 0, %reg to xor %reg, %reg
Date: Thu, 4 Aug 2022 15:26:54 +0000 [thread overview]
Message-ID: <20220804152656.8840-1-knscarlet@gnuweeb.org> (raw)
Hello Linux x86 maintainers,
I'm an informatic student 19 y.o. I am still studying Linux kernel open
source in GNU/Weeb community. I want to be a linux kerne dev in the
future. This is my first time sending a patch to Linux Kernel, I am
still learning the community. I may make a mistake in this email, please
correct me if i am wrong
I want to improve x86-64 assembly code with this patch. This patch
changes mov $0, %reg with xor %reg, %reg because xor %reg, %reg is
smaller so it is good to save space
asm:
ba 00 00 00 00 mov $0x0,%edx
31 d2 xor %edx,%edx
Regards,
Signed-off-by: Kanna Scarlet <knscarlet@gnuweeb.org>
---
Kanna Scarlet (1):
x86: Change mov $0, %reg with xor %reg, %reg
arch/x86/boot/compressed/head_64.S | 2 +-
arch/x86/boot/compressed/mem_encrypt.S | 2 +-
arch/x86/kernel/ftrace_32.S | 4 ++--
arch/x86/kernel/head_64.S | 2 +-
arch/x86/math-emu/div_Xsig.S | 2 +-
arch/x86/math-emu/reg_u_sub.S | 2 +-
6 files changed, 7 insertions(+), 7 deletions(-)
base-commit: ff89dd08c0f0a3fd330c9ef9d775e880f82c291e
--
Kanna Scarlet
next reply other threads:[~2022-08-04 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 15:26 Kanna Scarlet [this message]
2022-08-04 15:26 ` [PATCH 1/1] x86: Change mov $0, %reg with xor %reg, %reg Kanna Scarlet
2022-08-04 15:53 ` Borislav Petkov
2022-08-04 18:08 ` Kanna Scarlet
2022-08-05 9:26 ` David Laight
2022-08-05 9:42 ` Joerg Roedel
2022-08-08 16:45 ` Kanna Scarlet
2022-08-08 18:59 ` H. Peter Anvin
2022-08-08 16:38 ` Kanna Scarlet
2022-08-08 18:59 ` H. Peter Anvin
2022-08-09 7:38 ` David Laight
2022-08-05 9:54 ` Borislav Petkov
2022-08-08 16:57 ` Kanna Scarlet
-- strict thread matches above, loose matches on Subject: below --
2022-08-08 17:24 [PATCH 0/1] x86: change mov 0, %reg to " Alexey Dobriyan
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=20220804152656.8840-1-knscarlet@gnuweeb.org \
--to=knscarlet@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=ardb@kernel.org \
--cc=billm@melbpc.org.au \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=gwml@vger.gnuweeb.org \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=jroedel@suse.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.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