kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "Jorge Lucángeli Obes" <t4m5yn@gmail.com>,
	"Aidan Marks" <aidan@cisco.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH] x86: Pick up local arch trace header
Date: Thu, 24 Sep 2009 10:44:49 +0300	[thread overview]
Message-ID: <4ABB2371.7010701@redhat.com> (raw)
In-Reply-To: <4ABB14D1.1030508@web.de>

On 09/24/2009 09:42 AM, Jan Kiszka wrote:
> Jorge Lucángeli Obes wrote:
>    
>> ...
>> Aidan, were you able to solve this? I was having the same (original)
>> problem in Xubuntu 64-bits with a custom 2.6.31 kernel and kvm-88. I
>> still haven't tried Jan's patch (paper deadline at work) but I wanted
>> to know if you had made any progress.
>>      
> The kvm-kmod tree at git://git.kiszka.org/kvm-kmod.git (branch 'queue')
> meanwhile contains patches that solved all Aidan's build problems.
>
>    

Can you post them as patches please?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


      parent reply	other threads:[~2009-09-24  7:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19  2:19 kvm-kmod 88 or git not working with 2.6.31 Aidan Marks
2009-09-19  7:13 ` [PATCH] x86: Pick up local arch trace header (was: kvm-kmod 88 or git not working with 2.6.31) Jan Kiszka
2009-09-19 21:44   ` [PATCH] x86: Pick up local arch trace header Aidan Marks
2009-09-20  8:56     ` Jan Kiszka
2009-09-20 11:02       ` Aidan Marks
2009-09-20 11:42         ` Jan Kiszka
2009-09-20 12:55           ` Aidan Marks
2009-09-20 13:24             ` Jan Kiszka
2009-09-20 13:49               ` Aidan Marks
2009-09-23 19:28                 ` Jorge Lucángeli Obes
2009-09-24  6:42                   ` Jan Kiszka
2009-09-24  7:04                     ` Jorge Lucángeli Obes
2009-09-24  7:44                     ` Avi Kivity [this message]

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=4ABB2371.7010701@redhat.com \
    --to=avi@redhat.com \
    --cc=aidan@cisco.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=t4m5yn@gmail.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).