qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: xming <xmingske@gmail.com>, Gerd Hoffmann <kraxel@redhat.com>,
	kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: kvm crashes with spice while loading qxl
Date: Sun, 27 Feb 2011 21:32:36 +0200	[thread overview]
Message-ID: <20110227193236.GF14445@playa.redhat.com> (raw)
In-Reply-To: <4D6AA585.4020204@web.de>

On Sun, Feb 27, 2011 at 08:27:01PM +0100, Jan Kiszka wrote:
> On 2011-02-27 20:16, Alon Levy wrote:
> > On Sun, Feb 27, 2011 at 08:11:26PM +0100, Jan Kiszka wrote:
> >> On 2011-02-27 20:03, Alon Levy wrote:
> >>> On Sat, Feb 26, 2011 at 01:29:01PM +0100, Jan Kiszka wrote:
> >>>> On 2011-02-26 12:43, xming wrote:
> >>>>> When trying to start X (and it loads qxl driver) the kvm process just crashes.
> >>>
> >>> This is fixed by Gerd's attached patch (taken from rhel repository, don't know
> >>> why it wasn't pushed to qemu-kvm upstream). I'll send it to kvm list as well (separate email).
> >>
> >> Patch looks OK on first glance, but the changelog is misleading: This
> >> was broken for _both_ trees, but upstream didn't detect the bug.
> >>
> > 
> > The trees the patch commit message refers to are qemu and qemu-kvm.
> 
> The same did I.
> 
> > qemu doesn't even have cpu_single_env.
> 
> Really? Check again. :)
> 
> > It didn't talk about two qemu-kvm trees.
> > 
> >> My concerns regarding other side effects of juggling with global mutex
> >> in spice code remain.
> > 
> > I know there used to be a mutex in spice code and during the upstreaming process it
> > got ditched in favor of the qemu global io mutex. I would have rather deferred this
> > to Gerd since he wrote this, but he is not available atm.
> 
> It's not necessarily bad to drop the io mutex, but it is more tricky
> than it may appear on first glance.

The problem with not dropping it is that we may be in vga mode and create
updates synthtically (i.e. qemu created and not driver created) that access the
framebuffer and need to be locked so the framebuffer isn't updated at the same
time. We drop the mutex only when we are about to call the dispatcher, which basically
waits on red_worker (a libspice-server thread) to do some work. red_worker may
in turn callback into qxl in qemu, which may try to acquire the lock. (the
many may's here are just reflections of the codepaths).

> 
> Jan
> 

  parent reply	other threads:[~2011-02-27 19:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTint9-P-1jD5pbXstzPcYueLHQ68Rd0T_Chz6xRN@mail.gmail.com>
2011-02-26 12:29 ` [Qemu-devel] Re: kvm crashes with spice while loading qxl Jan Kiszka
2011-02-26 14:44   ` xming
2011-02-27 19:03   ` Alon Levy
2011-02-27 19:11     ` Jan Kiszka
2011-02-27 19:16       ` Alon Levy
2011-02-27 19:27         ` Jan Kiszka
2011-02-27 19:29           ` Alon Levy
2011-02-27 19:32           ` Alon Levy [this message]
2011-03-01 12:58       ` Alon Levy
2011-03-02  8:22         ` Jan Kiszka
2011-03-02 10:56           ` Alon Levy
2011-03-02 11:34             ` Jan Kiszka
2011-03-02 12:32               ` Alon Levy
2011-02-28 12:56     ` xming
2011-03-01  3:56     ` Rick Vernam
2011-03-05 16:35   ` Marcelo Tosatti
2011-03-05 17:11     ` Paolo Bonzini
2011-03-06 10:30     ` Alon Levy
2011-03-07 16:02       ` Marcelo Tosatti
2011-03-06 10:38     ` Avi Kivity
2011-03-07 16:13       ` Marcelo Tosatti
2011-03-07 22:27         ` Paolo Bonzini
2011-03-08  9:17         ` Avi Kivity
2011-03-08  9:28           ` Paolo Bonzini
2011-03-08  9:32             ` Avi Kivity
2011-04-26  8:53   ` [Qemu-devel] " Gerd Hoffmann
2011-04-26  9:06     ` Jan Kiszka
2011-04-26  9:43       ` Gerd Hoffmann
2011-04-26  9:34     ` Alon Levy

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=20110227193236.GF14445@playa.redhat.com \
    --to=alevy@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=xmingske@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).