From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH] KVM: Qemu: Do not use log dirty in IA64
Date: Wed, 01 Apr 2009 08:58:25 +0000 [thread overview]
Message-ID: <49D32CB1.1090100@redhat.com> (raw)
In-Reply-To: <10C63FAD690C13458F0B32BCED571F140E328C16@pdsmsx502.ccr.corp.intel.com>
Zhang, Yang wrote:
> hi
> please checkin it to kvm85, thanks!
>
> IA64 does not support log dirty. We should not use it
> in IA64, or it will have some problem.
>
Applied, thanks. When are you planning to add support for log dirty on
ia64?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: "Zhang, Yang" <yang.zhang@intel.com>
Cc: "kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH] KVM: Qemu: Do not use log dirty in IA64
Date: Wed, 01 Apr 2009 11:58:25 +0300 [thread overview]
Message-ID: <49D32CB1.1090100@redhat.com> (raw)
In-Reply-To: <10C63FAD690C13458F0B32BCED571F140E328C16@pdsmsx502.ccr.corp.intel.com>
Zhang, Yang wrote:
> hi
> please checkin it to kvm85, thanks!
>
> IA64 does not support log dirty. We should not use it
> in IA64, or it will have some problem.
>
Applied, thanks. When are you planning to add support for log dirty on
ia64?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-04-01 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 3:55 [PATCH] KVM: Qemu: Do not use log dirty in IA64 Zhang, Yang
2009-03-27 3:55 ` Zhang, Yang
2009-04-01 8:58 ` Avi Kivity [this message]
2009-04-01 8:58 ` Avi Kivity
2009-04-01 10:13 ` Zhang, Xiantao
2009-04-01 10:13 ` Zhang, Xiantao
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=49D32CB1.1090100@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.org \
/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.