From: Anthony Jagers <noonetinone@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Fwd: Later Kernel versions break some games in wine
Date: Fri, 25 Jan 2019 11:38:51 -0500 [thread overview]
Message-ID: <CANKW2PSs8n8pTw8fmO2QrgjGO5Rmes7NW4d2D_MUncoeCheS7w@mail.gmail.com> (raw)
In-Reply-To: <CANKW2PR-aN=2GhkK0kLjuFiPoceffGS-E5euBFkytV2bK5h3zg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 865 bytes --]
---------- Forwarded message ---------
From: Anthony Jagers <noonetinone@gmail.com>
Date: Fri, Jan 25, 2019 at 11:35 AM
Subject: Later Kernel versions break some games in wine
To: <majordomo@vger.kernel.org>
Changes in PTRACE_POKEUSER hw breakpoint have broken several games that are
being ran through wine.
I must point out that I did not do the bisect, the OP in the wine bug
report below did that.
I brought this here because of the dislike among developers in breaking
user space. I don't
know how to proceed from here. Either, wine should adopt code changes or
the commit below should
be reverted.
commit bd14406b78e6daa1ea3c1673bda1ffc9efdeead0
Author: Jiri Olsa <jolsa@kernel.org>
Date: Mon Aug 27 11:12:25 2018 +0200
perf/hw_breakpoint: Modify breakpoint even if the new attr has disabled
set
+++
https://bugs.winehq.org/show_bug.cgi?id=46472
[-- Attachment #1.2: Type: text/html, Size: 1535 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next parent reply other threads:[~2019-01-26 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANKW2PR-aN=2GhkK0kLjuFiPoceffGS-E5euBFkytV2bK5h3zg@mail.gmail.com>
2019-01-25 16:38 ` Anthony Jagers [this message]
2019-01-27 8:29 ` Fwd: Later Kernel versions break some games in wine Greg KH
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=CANKW2PSs8n8pTw8fmO2QrgjGO5Rmes7NW4d2D_MUncoeCheS7w@mail.gmail.com \
--to=noonetinone@gmail.com \
--cc=kernelnewbies@kernelnewbies.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).