From: lijiang <lijiang@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
tglx@linutronix.de, mingo@redhat.com, akpm@linux-foundation.org,
x86@kernel.org, hpa@zytor.com, dyoung@redhat.com, bhe@redhat.com,
Thomas.Lendacky@amd.com, brijesh.singh@amd.com
Subject: Re: [PATCH 1/3 v2] x86/kexec: Do not map the kexec area as decrypted when SEV is active
Date: Sun, 28 Apr 2019 09:29:00 +0800 [thread overview]
Message-ID: <16ca1636-5025-82a5-fe22-2b409e8e515f@redhat.com> (raw)
In-Reply-To: <20190426130226.GE4608@zn.tnic>
在 2019年04月26日 21:02, Borislav Petkov 写道:
> On Fri, Apr 26, 2019 at 09:59:54AM +0800, lijiang wrote:
>> Hope this help. Thanks.
>
> It does help, yes. When this explanation above is part of the commit
> message, it helps immensely!
OK, i will add them to the commit message and post again.
>
> :-)
>
>> So sorry for the delay, i am trying my best to explain it in detail.
>
> I don't care about the delay as long as the commit messages properly
> explain why the change is needed.
>
> So thanks for doing that.
>
It's my pleasure. Thanks.
Lianbo
next prev parent reply other threads:[~2019-04-28 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 5:36 [PATCH 0/3 v2] Add kdump support for the SEV enabled guest Lianbo Jiang
2019-03-27 5:36 ` [PATCH 1/3 v2] x86/kexec: Do not map the kexec area as decrypted when SEV is active Lianbo Jiang
2019-04-02 10:32 ` Borislav Petkov
2019-04-26 1:59 ` lijiang
2019-04-26 13:02 ` Borislav Petkov
2019-04-28 1:29 ` lijiang [this message]
2019-03-27 5:36 ` [PATCH 2/3 v2] x86/kexec: Set the C-bit in the identity map page table " Lianbo Jiang
2019-03-27 5:36 ` [PATCH 3/3 v2] kdump,proc/vmcore: Enable kdumping encrypted memory when SEV was active Lianbo Jiang
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=16ca1636-5025-82a5-fe22-2b409e8e515f@redhat.com \
--to=lijiang@redhat.com \
--cc=Thomas.Lendacky@amd.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--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®