From: Erik Rull <erik.rull@rdsoftware.de>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] git bisect results
Date: Sat, 28 Jan 2012 14:01:10 +0100 [thread overview]
Message-ID: <4F23F196.9040404@rdsoftware.de> (raw)
In-Reply-To: <4F23ED6A.1010602@web.de>
Jan Kiszka wrote:
> On 2012-01-28 13:39, Erik Rull wrote:
>> Jan Kiszka wrote:
>>> On 2012-01-27 23:52, Jan Kiszka wrote:
>>>> On 2012-01-26 14:10, Erik Rull wrote:
>>>>> I assume from these results that the gui_grab is never set to 1 when
>>>>> having
>>>>> entered the window in windowed mode with the cursor.
>>>>>
>>>>> Maybe that's why the sdl_grab_start() is called so often.
>>>>>
>>>>> It seems that the condition in sdl_grab_start()
>>>>> (SDL_WM_GrabInput(SDL_GRAB_ON)
>>>>> == SDL_GRAB_ON) is never fulfilled, otherwise the gui_grab would be
>>>>> set to 1.
>>>>> But the cursor is actually grabbed in windowed mode, otherwise I
>>>>> would not be
>>>>> able to click somewhere with the guest-windows-cursor.
>>>>
>>>> This might be a SDL limitation which does not show up everywhere. Here
>>>> it's fine e.g.
>>>>
>>>> The logic dates back to "Handle SDL grabs failing (Mark McLoughlin)",
>>>> 6bb816031f. Maybe we can solve that issue without relying on the
>>>> obviously unreliable return value. Need to reproduce that one as well,
>>>> though.
>>>
>>> Please check if
>>>
>>> git://git.kiszka.org/qemu.git queues/sdl
>>>
>>> fixes the issue for you. Namely reverting the above commit should do the
>>> trick. I obsoleted that fragile patch in my series.
>>>
>>> Thanks,
>>> Jan
>>>
>>>
>>
>> Hi Jan,
>>
>> I will test this on monday. Can you tell me how I can merge that into my
>> cloned main qemu repository? I'm quite new to git.
>
> # git remote add kiszka git://git.kiszka.org/qemu.git
> # git fetch kiszka
> # git checkout kiszka/queues/sdl
>
> That way you will have what I have. Or do you need additional patches
> for your tests?
>
> Jan
>
No I think this will be sufficient. Will this work if I will add it to the
qemu-kvm-1.0 tagged version? I have further issues when using the current
master because this version does not boot up Windows XP at the moment. I
was not able to bisect up to now where this issue was added.
Best regards,
Erik
next prev parent reply other threads:[~2012-01-28 13:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 13:10 [Qemu-devel] git bisect results Erik Rull
2012-01-26 16:24 ` Jan Kiszka
2012-01-27 22:52 ` Jan Kiszka
2012-01-28 11:55 ` Jan Kiszka
2012-01-28 12:39 ` Erik Rull
2012-01-28 12:43 ` Jan Kiszka
2012-01-28 13:01 ` Erik Rull [this message]
2012-01-28 14:52 ` Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2012-01-30 11:34 Erik Rull
2012-01-30 11:52 ` Jan Kiszka
2012-01-30 13:17 ` Erik Rull
2012-01-30 13:48 ` Jan Kiszka
2012-01-30 14:17 ` Erik Rull
2012-01-30 14:48 ` Jan Kiszka
2012-01-31 8:31 ` Erik Rull
2012-01-25 11:48 erik.rull
2012-01-25 14:19 ` Jan Kiszka
2012-01-25 21:13 ` Erik Rull
2012-01-23 8:57 [Qemu-devel] bad USB tablet update rate on qemu-1.0 erik.rull
2012-01-24 17:24 ` [Qemu-devel] git bisect results (was: Re: bad USB tablet update rate on qemu-1.0) Erik Rull
2012-01-24 18:19 ` [Qemu-devel] git bisect results Jan Kiszka
2012-01-24 18:55 ` Erik Rull
2012-01-24 20:15 ` 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=4F23F196.9040404@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.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 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).