Adam Steen writes:
> Hi
>
> IA32_EPT_VPID_CAP_XO_TRANSLATIONS is specified incorrectly, see the
> patch below.
Adam's diff looks correct to me based on reading Intel SDM Vol 3D,
Appendix A.10 (VPID and EPT Capabilities) [1]:
The IA32_VMX_EPT_VPID_CAP MSR (index 48CH) reports information
On Tue, Mar 23, 2021 at 08:24:56PM +1000, David Gwynne wrote:
> it looks like ure(4) hardware doesn't strip the fcs before pushing it to
> the host over usb, but the ure(4) driver doesn't strip it.
>
> this usually isn't a huge deal because layers like ip just ignore
> the extra bytes. bridge(4)
Hello.
I get reports from people seeing "vfprintf %s NULL" in their logs
recently. The problem is in a function that should be fixed,
but that function is only expected to but used for debug traces.
This diff turns log_trace() into a macro, so the parameters
are not needlessly evaluated when
On Fri, Mar 26, 2021 at 1:56 PM Alexander Bluhm wrote:
>
> On Mon, Mar 22, 2021 at 08:38:23PM -0500, Brent Cook wrote:
> > In the next version of Linux glibc, SIGSTKSZ is defined at runtime if
> > source is built with _GNU_SOURCE. On LibreSSL-portable, this is set to
> > bring in
On Fri, Mar 26, 2021 at 03:41:41PM -0500, joshua stein wrote:
> The X server's autoconfiguration probes each /dev/wsmouseN device
> and if its WSMOUSEIO_GTYPE ioctl returns something like
> WSMOUSE_TYPE_TOUCHPAD, xf86-input-ws attaches to that device
> directly which causes the wsmouse device
Patch #367 - 2021/03/26
* add OSC 22 to allow programs to select different pointer cursor at
runtime.
* change configuration for no-return functions to use _Noreturn when
it is available, because clang --analyze does not properly handle
> Feel free to share your raw data.
Also includes some standard sendbug dumps: https://0x0.st/-qng.tgz
