From: tip-bot for Cao jin <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: caoj.fnst@cn.fujitsu.com, linux-kernel@vger.kernel.org,
hpa@zytor.com, mingo@kernel.org, kirill.shutemov@linux.intel.com,
tglx@linutronix.de, bp@alien8.de
Subject: [tip:x86/cleanups] x86/boot: Save several bytes in decompressor
Date: Tue, 29 Jan 2019 13:13:32 -0800 [thread overview]
Message-ID: <tip-0a278662f53159354a0391a17741a20db736256a@git.kernel.org> (raw)
In-Reply-To: <20190123100014.23721-1-caoj.fnst@cn.fujitsu.com>
Commit-ID: 0a278662f53159354a0391a17741a20db736256a
Gitweb: https://git.kernel.org/tip/0a278662f53159354a0391a17741a20db736256a
Author: Cao jin <caoj.fnst@cn.fujitsu.com>
AuthorDate: Wed, 23 Jan 2019 18:00:14 +0800
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 29 Jan 2019 22:09:12 +0100
x86/boot: Save several bytes in decompressor
gdt64 represents the content of GDTR under x86-64, which actually needs
10 bytes only, ".long" & ".word" is superfluous.
Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Cc: <bp@alien8.de>
Cc: <hpa@zytor.com>
Link: https://lkml.kernel.org/r/20190123100014.23721-1-caoj.fnst@cn.fujitsu.com
---
arch/x86/boot/compressed/head_64.S | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/boot/compressed/head_64.S b/arch/x86/boot/compressed/head_64.S
index 64037895b085..b27b338d2f6d 100644
--- a/arch/x86/boot/compressed/head_64.S
+++ b/arch/x86/boot/compressed/head_64.S
@@ -645,8 +645,6 @@ no_longmode:
.data
gdt64:
.word gdt_end - gdt
- .long 0
- .word 0
.quad 0
gdt:
.word gdt_end - gdt
prev parent reply other threads:[~2019-01-29 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 10:00 [PATCH] x86/boot: save " Cao jin
2019-01-23 10:05 ` Kirill A. Shutemov
2019-01-29 21:13 ` tip-bot for Cao jin [this message]
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=tip-0a278662f53159354a0391a17741a20db736256a@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bp@alien8.de \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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®