From: Nathan Chancellor <nathan@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: xiafukun <xiafukun@huawei.com>,
arnd@arndb.de, keescook@chromium.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, yusongping@huawei.com,
zhaowenhui8@huawei.comx
Subject: Re: vmlinux.lds.h: Bug report: unable to handle page fault when start the virtual machine with qemu
Date: Tue, 8 Nov 2022 08:16:55 -0700 [thread overview]
Message-ID: <Y2py5533IW9RTUZD@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CAMj1kXGm=OXs=fw2UY7xgLP-m_gsfgW56xEmFRAm74z5+bd8Ow@mail.gmail.com>
On Tue, Nov 08, 2022 at 04:14:44PM +0100, Ard Biesheuvel wrote:
> On Tue, 8 Nov 2022 at 15:35, Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > On Tue, Nov 08, 2022 at 03:46:32PM +0800, xiafukun wrote:
> > > Thank you for your reply.
> > > We tested your changes to this patch and did fix the issue. Following the
> > > solution you provided, we recompile the kernel and successfully start the
> > > virtual machine.
> >
> > Thank you a lot for testing and sorry about the breakage in the first
> > place :(
> >
> > Ard, were you going to send a patch? Feel free to preemptively add:
> >
> > Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> >
> > if so; otherwise, I can send one later today.
> >
>
> If you don't mind?
Not at all, since it is my issue and you did the hard work for me :)
Will send it out in a little bit, thanks again for the assist!
Cheers,
Nathan
prev parent reply other threads:[~2022-11-08 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 3:27 vmlinux.lds.h: Bug report: unable to handle page fault when start the virtual machine with qemu zhaowenhui (A)
2022-11-07 16:00 ` Ard Biesheuvel
2022-11-08 7:46 ` xiafukun
2022-11-08 14:35 ` Nathan Chancellor
2022-11-08 15:14 ` Ard Biesheuvel
2022-11-08 15:16 ` Nathan Chancellor [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=Y2py5533IW9RTUZD@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiafukun@huawei.com \
--cc=yusongping@huawei.com \
--cc=zhaowenhui8@huawei.comx \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.