From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Scott Wood <scottwood@freescale.com>,
kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/2] KVM: PPC: e500: fix allocation size error on g2h_tlb1_map
Date: Tue, 02 Oct 2012 10:22:24 +0000 [thread overview]
Message-ID: <506AC060.1040409@redhat.com> (raw)
In-Reply-To: <5E691359-FE1B-47C7-A8A7-A2CC04D8A013@suse.de>
On 10/01/2012 12:59 PM, Alexander Graf wrote:
>
> On 30.09.2012, at 13:29, Avi Kivity wrote:
>
>> On 09/27/2012 09:59 PM, Alexander Graf wrote:
>>>
>>>> Do you have the auto-autotest setup ready? I guess we can do it
>>>> manually until it is.
>>>
>>> I do have a local autotest setup. Or what exactly are you referring to?
>>
>> Getting autotest to run automatically and produce readable reports, and
>> auto-bisection.
>
> I'm not quite there yet :). Do you have any precooked things I could reuse?
Nope, currently we eat from the tin.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Scott Wood <scottwood@freescale.com>,
kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/2] KVM: PPC: e500: fix allocation size error on g2h_tlb1_map
Date: Tue, 02 Oct 2012 12:22:24 +0200 [thread overview]
Message-ID: <506AC060.1040409@redhat.com> (raw)
In-Reply-To: <5E691359-FE1B-47C7-A8A7-A2CC04D8A013@suse.de>
On 10/01/2012 12:59 PM, Alexander Graf wrote:
>
> On 30.09.2012, at 13:29, Avi Kivity wrote:
>
>> On 09/27/2012 09:59 PM, Alexander Graf wrote:
>>>
>>>> Do you have the auto-autotest setup ready? I guess we can do it
>>>> manually until it is.
>>>
>>> I do have a local autotest setup. Or what exactly are you referring to?
>>
>> Getting autotest to run automatically and produce readable reports, and
>> auto-bisection.
>
> I'm not quite there yet :). Do you have any precooked things I could reuse?
Nope, currently we eat from the tin.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-02 10:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 1:04 [PATCH 1/2] KVM: PPC: e500: fix allocation size error on g2h_tlb1_map Scott Wood
2012-08-23 1:04 ` Scott Wood
2012-08-23 1:04 ` [PATCH 2/2] KVM: PPC: e500: MMU API: fix leak of shared_tlb_pages Scott Wood
2012-08-23 1:04 ` Scott Wood
2012-09-25 7:46 ` Alexander Graf
2012-09-25 7:46 ` Alexander Graf
2012-09-25 7:46 ` [PATCH 1/2] KVM: PPC: e500: fix allocation size error on g2h_tlb1_map Alexander Graf
2012-09-25 7:46 ` Alexander Graf
2012-09-27 16:03 ` Marcelo Tosatti
2012-09-27 16:03 ` Marcelo Tosatti
2012-09-27 16:35 ` Avi Kivity
2012-09-27 16:35 ` Avi Kivity
2012-09-27 19:59 ` Alexander Graf
2012-09-27 19:59 ` Alexander Graf
2012-09-30 11:29 ` Avi Kivity
2012-09-30 11:29 ` Avi Kivity
2012-10-01 10:59 ` Alexander Graf
2012-10-01 10:59 ` Alexander Graf
2012-10-02 10:22 ` Avi Kivity [this message]
2012-10-02 10:22 ` Avi Kivity
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=506AC060.1040409@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=scottwood@freescale.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.