From: Zhao Liu <zhao1.liu@intel.com>
To: Wang Xin <wangxinxin.wang@huawei.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
weidong.huang@huawei.com, Tuo Xie <xietuo@huawei.com>
Subject: Re: [PATCH] target/i386: Add support save/load exception error_code
Date: Wed, 20 Aug 2025 18:05:00 +0800 [thread overview]
Message-ID: <aKWdzEt2zUByeMwH@intel.com> (raw)
In-Reply-To: <20250819145834.3998-1-wangxinxin.wang@huawei.com>
On Tue, Aug 19, 2025 at 10:58:34PM +0800, Wang Xin wrote:
> Date: Tue, 19 Aug 2025 22:58:34 +0800
> From: Wang Xin <wangxinxin.wang@huawei.com>
> Subject: [PATCH] target/i386: Add support save/load exception error_code
> X-Mailer: git-send-email 2.50.1.windows.1
>
> From: WangXin <wangxinxin.wang@huawei.com>
>
> For now, qemu save/load CPU exception info(such as exception_nr and
> has_error_code), while the exception error_code is ignored. This will
> cause the dest hypervisor reinject a vCPU exception with error_code(0),
> potentially causing a guest kernel panic.
>
> For instance, if src VM stopped with an user-mode write #PF (error_code 6),
> the dest hypervisor will reinject an #PF with error_code(0) when vCPU resume,
> then guest kernel panic as:
> BUG: unable to handle page fault for address: 00007f80319cb010
> #PF: supervisor read access in user mode
> #PF: error_code(0x0000) - not-present page
> RIP: 0033:0x40115d
>
> To fix it, support save/load exception error_code.
>
> Signed-off-by: Xin Wang <wangxinxin.wang@huawei.com>
> Signed-off-by: Tuo Xie <xietuo@huawei.com>
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
prev parent reply other threads:[~2025-08-20 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 14:58 [PATCH] target/i386: Add support save/load exception error_code Wang Xin via
2025-08-19 15:28 ` Paolo Bonzini
2025-08-20 2:18 ` Wangxin (Alexander) via
2025-08-20 10:16 ` zhao1.liu
2025-08-20 10:05 ` Zhao Liu [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=aKWdzEt2zUByeMwH@intel.com \
--to=zhao1.liu@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
--cc=xietuo@huawei.com \
/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.