From: Paolo Bonzini <pbonzini@redhat.com>
To: "Volker Rümelin" <vr_qemu@t-online.de>,
"Wenchao Wang" <wenchao.wang@intel.com>,
"Colin Xu" <colin.xu@intel.com>
Cc: Julio Faracco <jcfaracco@gmail.com>, QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH] hax: Windows doesn't like posix device names
Date: Mon, 23 Mar 2020 09:20:37 +0100 [thread overview]
Message-ID: <e38bcea7-4fce-724f-d154-d3ffc3d3d33f@redhat.com> (raw)
In-Reply-To: <20200322210211.29603-1-vr_qemu@t-online.de>
On 22/03/20 22:02, Volker Rümelin wrote:
> Patch acb9f95a7c "i386: Fix GCC warning with snprintf when HAX
> is enabled" replaced Windows device names with posix device
> names. Revert this.
>
> Fixes: acb9f95a7c "i386: Fix GCC warning with snprintf when HAX is enabled"
>
> Signed-off-by: Volker Rümelin <vr_qemu@t-online.de>
> ---
> target/i386/hax-windows.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target/i386/hax-windows.c b/target/i386/hax-windows.c
> index 0ba488c468..863c2bcc19 100644
> --- a/target/i386/hax-windows.c
> +++ b/target/i386/hax-windows.c
> @@ -185,12 +185,12 @@ int hax_mod_version(struct hax_state *hax, struct hax_module_version *version)
>
> static char *hax_vm_devfs_string(int vm_id)
> {
> - return g_strdup_printf("/dev/hax_vm/vm%02d", vm_id);
> + return g_strdup_printf("\\\\.\\hax_vm%02d", vm_id);
> }
>
> static char *hax_vcpu_devfs_string(int vm_id, int vcpu_id)
> {
> - return g_strdup_printf("/dev/hax_vm%02d/vcpu%02d", vm_id, vcpu_id);
> + return g_strdup_printf("\\\\.\\hax_vm%02d_vcpu%02d", vm_id, vcpu_id);
> }
>
> int hax_host_create_vm(struct hax_state *hax, int *vmid)
>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2020-03-23 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 21:02 [PATCH] hax: Windows doesn't like posix device names Volker Rümelin
2020-03-23 8:20 ` Paolo Bonzini [this message]
2020-04-09 13:24 ` Stefan Weil
2020-04-09 13:38 ` Paolo Bonzini
2020-04-10 9:21 ` Volker Rümelin
2020-04-13 18:17 ` Volker Rümelin
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=e38bcea7-4fce-724f-d154-d3ffc3d3d33f@redhat.com \
--to=pbonzini@redhat.com \
--cc=colin.xu@intel.com \
--cc=jcfaracco@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=vr_qemu@t-online.de \
--cc=wenchao.wang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).