From: Yan Zhao <yan.y.zhao@intel.com>
To: Baoquan He <bhe@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
<kexec@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-coco@lists.linux.dev>, <x86@kernel.org>,
<rick.p.edgecombe@intel.com>, <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] kexec_core: Accept unaccepted kexec destination addresses
Date: Wed, 4 Dec 2024 17:19:44 +0800 [thread overview]
Message-ID: <Z1AesNxMFwuZQ7WY@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <Z07dzP6ZdW3sNahj@MiWiFi-R3L-srv>
On Tue, Dec 03, 2024 at 06:30:36PM +0800, Baoquan He wrote:
> On 12/03/24 at 06:06pm, Yan Zhao wrote:
> > On Mon, Dec 02, 2024 at 10:17:16PM +0800, Baoquan He wrote:
> > > On 11/29/24 at 01:52pm, Yan Zhao wrote:
> > > > On Thu, Nov 28, 2024 at 11:19:20PM +0800, Baoquan He wrote:
...
> > > Oh, I just said the opposite. I meant we could search according to the
> > > current unaccepted->bitmap to make sure the destination area definitely
> > > have been accepted. This is the best if doable, while I know it's not
> > > easy.
> > Well, this sounds like introducing a new constraint in addition to the current
> > checking of !kimage_is_destination_range() in locate_mem_hole_top_down() or
> > locate_mem_hole_bottom_up(). (powerpc also has a different implementation).
> >
> > This could make the success unpredictable, depending on how many pages have
> > been accepted by the 1st kernel and the layout of the accepted pages(e.g.,
> > whether they are physically contiguous). The 1st kernel would also have no
> > reliable way to ensure success except by accepting all the guest pages.
>
> Yeah, when I finished reading accept_memory code, this is the first idea
> which come up into my mind. If it can be made, it's the most ideal. When
> I tried to make a draft change, it does introduce a lot of code change and
> add very much complication and I just gave up.
>
> Maybe this can be added to cover-letter too to tell this possible path we
> explored.
Ok.
next prev parent reply other threads:[~2024-12-04 9:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 3:45 Yan Zhao
2024-10-21 14:33 ` Eric W. Biederman
2024-10-22 3:12 ` Yan Zhao
2024-10-22 12:06 ` Kirill A. Shutemov
2024-10-23 15:44 ` Eric W. Biederman
2024-10-24 0:15 ` Yan Zhao
2024-10-24 0:26 ` Yan Zhao
2024-11-26 11:38 ` Baoquan He
2024-11-27 10:01 ` Yan Zhao
2024-11-28 15:19 ` Baoquan He
2024-11-29 5:52 ` Yan Zhao
2024-12-02 14:17 ` Baoquan He
2024-12-03 10:06 ` Yan Zhao
2024-12-03 10:30 ` Baoquan He
2024-12-04 9:19 ` Yan Zhao [this message]
2024-10-25 13:56 ` Kirill A. Shutemov
2024-11-04 8:35 ` Kirill A. Shutemov
2024-11-08 12:29 ` Kirill A. Shutemov
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=Z1AesNxMFwuZQ7WY@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=bhe@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--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®