From: Paolo Bonzini <pbonzini@redhat.com>
To: Roman Bolshakov <r.bolshakov@yadro.com>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Cameron Esfahani <dirty@apple.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 12/13] i386: hvf: Move mmio_buf into CPUX86State
Date: Thu, 4 Jun 2020 20:27:37 +0200 [thread overview]
Message-ID: <d57e48c6-574e-471c-78be-1245d62bc908@redhat.com> (raw)
In-Reply-To: <20200528193758.51454-13-r.bolshakov@yadro.com>
On 28/05/20 21:37, Roman Bolshakov wrote:
> There's no similar field in CPUX86State, but it's needed for MMIO traps.
>
> Signed-off-by: Roman Bolshakov <r.bolshakov@yadro.com>
> ---
> target/i386/cpu.h | 1 +
> target/i386/hvf/hvf.c | 5 +++++
> target/i386/hvf/x86.h | 1 -
> target/i386/hvf/x86_emu.c | 12 ++++++------
> 4 files changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/target/i386/cpu.h b/target/i386/cpu.h
> index 7e6566565a..be44e19154 100644
> --- a/target/i386/cpu.h
> +++ b/target/i386/cpu.h
> @@ -1593,6 +1593,7 @@ typedef struct CPUX86State {
> #endif
> #if defined(CONFIG_HVF)
> hvf_lazy_flags hvf_lflags;
> + void *hvf_mmio_buf;
> HVFX86EmulatorState *hvf_emul;
> #endif
>
> diff --git a/target/i386/hvf/hvf.c b/target/i386/hvf/hvf.c
> index 4cee496d71..57696c46c7 100644
> --- a/target/i386/hvf/hvf.c
> +++ b/target/i386/hvf/hvf.c
> @@ -533,7 +533,11 @@ void hvf_reset_vcpu(CPUState *cpu) {
>
> void hvf_vcpu_destroy(CPUState *cpu)
> {
> + X86CPU *x86_cpu = X86_CPU(cpu);
> + CPUX86State *env = &x86_cpu->env;
> +
> hv_return_t ret = hv_vcpu_destroy((hv_vcpuid_t)cpu->hvf_fd);
> + g_free(env->hvf_mmio_buf);
> assert_hvf_ok(ret);
> }
>
> @@ -563,6 +567,7 @@ int hvf_init_vcpu(CPUState *cpu)
> init_decoder();
>
> hvf_state->hvf_caps = g_new0(struct hvf_vcpu_caps, 1);
> + env->hvf_mmio_buf = g_new(char, 4096);
> env->hvf_emul = g_new0(HVFX86EmulatorState, 1);
>
> r = hv_vcpu_create((hv_vcpuid_t *)&cpu->hvf_fd, HV_VCPU_DEFAULT);
> diff --git a/target/i386/hvf/x86.h b/target/i386/hvf/x86.h
> index 2363616c07..483fcea762 100644
> --- a/target/i386/hvf/x86.h
> +++ b/target/i386/hvf/x86.h
> @@ -230,7 +230,6 @@ typedef struct x68_segment_selector {
>
> /* Definition of hvf_x86_state is here */
> struct HVFX86EmulatorState {
> - uint8_t mmio_buf[4096];
> };
>
> /* useful register access macros */
> diff --git a/target/i386/hvf/x86_emu.c b/target/i386/hvf/x86_emu.c
> index 1ad2c30e16..d3e289ed87 100644
> --- a/target/i386/hvf/x86_emu.c
> +++ b/target/i386/hvf/x86_emu.c
> @@ -187,8 +187,8 @@ void write_val_ext(struct CPUX86State *env, target_ulong ptr, target_ulong val,
>
> uint8_t *read_mmio(struct CPUX86State *env, target_ulong ptr, int bytes)
> {
> - vmx_read_mem(env_cpu(env), env->hvf_emul->mmio_buf, ptr, bytes);
> - return env->hvf_emul->mmio_buf;
> + vmx_read_mem(env_cpu(env), env->hvf_mmio_buf, ptr, bytes);
> + return env->hvf_mmio_buf;
> }
>
>
> @@ -489,9 +489,9 @@ static void exec_ins_single(struct CPUX86State *env, struct x86_decode *decode)
> target_ulong addr = linear_addr_size(env_cpu(env), RDI(env),
> decode->addressing_size, R_ES);
>
> - hvf_handle_io(env_cpu(env), DX(env), env->hvf_emul->mmio_buf, 0,
> + hvf_handle_io(env_cpu(env), DX(env), env->hvf_mmio_buf, 0,
> decode->operand_size, 1);
> - vmx_write_mem(env_cpu(env), addr, env->hvf_emul->mmio_buf,
> + vmx_write_mem(env_cpu(env), addr, env->hvf_mmio_buf,
> decode->operand_size);
>
> string_increment_reg(env, R_EDI, decode);
> @@ -512,9 +512,9 @@ static void exec_outs_single(struct CPUX86State *env, struct x86_decode *decode)
> {
> target_ulong addr = decode_linear_addr(env, decode, RSI(env), R_DS);
>
> - vmx_read_mem(env_cpu(env), env->hvf_emul->mmio_buf, addr,
> + vmx_read_mem(env_cpu(env), env->hvf_mmio_buf, addr,
> decode->operand_size);
> - hvf_handle_io(env_cpu(env), DX(env), env->hvf_emul->mmio_buf, 1,
> + hvf_handle_io(env_cpu(env), DX(env), env->hvf_mmio_buf, 1,
> decode->operand_size, 1);
>
> string_increment_reg(env, R_ESI, decode);
>
It should be possible to get rid of the buffer altogether, but it's ok
to do it separately.
I queued the series, thanks.
Paolo
next prev parent reply other threads:[~2020-06-04 18:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 19:37 [PATCH 00/13] i386: hvf: Remove HVFX86EmulatorState Roman Bolshakov
2020-05-28 19:37 ` [PATCH 01/13] i386: hvf: Move HVFState definition into hvf Roman Bolshakov
2020-06-05 14:19 ` Claudio Fontana
2020-05-28 19:37 ` [PATCH 02/13] i386: hvf: Drop useless declarations in sysemu Roman Bolshakov
2020-06-04 6:35 ` Philippe Mathieu-Daudé
2020-06-04 9:53 ` Claudio Fontana
2020-06-05 16:30 ` Roman Bolshakov
2020-05-28 19:37 ` [PATCH 03/13] i386: hvf: Clean stray includes " Roman Bolshakov
2020-06-05 14:20 ` Claudio Fontana
2020-05-28 19:37 ` [PATCH 04/13] i386: hvf: Drop unused variable Roman Bolshakov
2020-06-04 6:35 ` Philippe Mathieu-Daudé
2020-05-28 19:37 ` [PATCH 05/13] i386: hvf: Use ins_len to advance IP Roman Bolshakov
2020-06-04 6:39 ` Philippe Mathieu-Daudé
2020-06-04 18:15 ` Paolo Bonzini
2020-06-05 14:29 ` Philippe Mathieu-Daudé
2020-05-28 19:37 ` [PATCH 06/13] i386: hvf: Use IP from CPUX86State Roman Bolshakov
2020-06-04 6:47 ` Philippe Mathieu-Daudé
2020-06-04 9:06 ` Claudio Fontana
2020-05-28 19:37 ` [PATCH 07/13] i386: hvf: Drop fetch_rip from HVFX86EmulatorState Roman Bolshakov
2020-05-28 19:37 ` [PATCH 08/13] i386: hvf: Drop rflags " Roman Bolshakov
2020-05-28 19:37 ` [PATCH 09/13] i386: hvf: Drop copy of RFLAGS defines Roman Bolshakov
2020-05-28 19:37 ` [PATCH 10/13] i386: hvf: Drop regs in HVFX86EmulatorState Roman Bolshakov
2020-05-28 19:37 ` [PATCH 11/13] i386: hvf: Move lazy_flags into CPUX86State Roman Bolshakov
2020-06-04 6:43 ` Philippe Mathieu-Daudé
2020-05-28 19:37 ` [PATCH 12/13] i386: hvf: Move mmio_buf " Roman Bolshakov
2020-06-04 18:27 ` Paolo Bonzini [this message]
2020-06-05 17:24 ` Roman Bolshakov
2020-06-11 13:24 ` Claudio Fontana
2020-06-11 15:02 ` Roman Bolshakov
2020-05-28 19:37 ` [PATCH 13/13] i386: hvf: Drop HVFX86EmulatorState Roman Bolshakov
2020-05-29 2:57 ` [PATCH 00/13] i386: hvf: Remove HVFX86EmulatorState no-reply
2020-06-04 1:53 ` Cameron Esfahani
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=d57e48c6-574e-471c-78be-1245d62bc908@redhat.com \
--to=pbonzini@redhat.com \
--cc=dirty@apple.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
--cc=rth@twiddle.net \
/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).