public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Tsuyoshi Ozawa <ozawa@t-oza.net>
Cc: KVM ML <kvm@vger.kernel.org>
Subject: Re: [PATCH] Build fix for #define KVM_DEBUG
Date: Tue, 09 Feb 2010 12:27:11 +0200	[thread overview]
Message-ID: <4B71387F.4000203@redhat.com> (raw)
In-Reply-To: <411a180c1002082240u520516fck3cb93372626c5a77@mail.gmail.com>

On 02/09/2010 08:40 AM, Tsuyoshi Ozawa wrote:
> Build fix for #define KVM_DEBUG
>
> If KVM_DEBUG is defined, the build for kvm_kmod is failed because :
>
> 1. is_long_mode() has moved to x86.h.
> 2. shadow_efer no longer exists.
> 3. The registers R8 - R15 don't exist on i386 architecture.
>
> This patch fix this problem.
>
>
>          VMCS_REG_DUMP(RSP);
>          VMCS_REG_DUMP(RIP);
> @@ -1088,7 +1091,6 @@ void sregs_dump(struct kvm_vcpu *vcpu)
>          vcpu_printf(vcpu, "cr3 = 0x%lx\n", vcpu->arch.cr3);
>          vcpu_printf(vcpu, "cr4 = 0x%lx\n", vcpu->arch.cr4);
>          vcpu_printf(vcpu, "cr8 = 0x%lx\n", vcpu->arch.cr8);
> -       vcpu_printf(vcpu, "shadow_efer = 0x%llx\n", vcpu->arch.shadow_efer);
>          vcpu_printf(vcpu,
>    

shadow_efer was renamed to efer, so this should be modified rather than 
deleted.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-02-09 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09  6:40 [PATCH] Build fix for #define KVM_DEBUG Tsuyoshi Ozawa
2010-02-09 10:27 ` Avi Kivity [this message]
2010-02-09 10:51   ` Tsuyoshi Ozawa
2010-02-17  2:41     ` Tsuyoshi Ozawa
2010-02-17 10:46       ` Avi Kivity
2010-02-17 11:40         ` Jan Kiszka

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=4B71387F.4000203@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=ozawa@t-oza.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