From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Broken PCI device passthrough, after XSA-302 fix?
Date: Mon, 6 Jan 2020 17:37:31 +0100 [thread overview]
Message-ID: <20200106163731.GM1314@mail-itl> (raw)
In-Reply-To: <a044a991-0a28-6b64-8046-2338b40172d6@suse.com>
[-- Attachment #1.1: Type: text/plain, Size: 675 bytes --]
On Mon, Jan 06, 2020 at 03:38:46PM +0100, Jan Beulich wrote:
> On 06.01.2020 15:04, Marek Marczykowski-Górecki wrote:
> > Is the patch from your other message still relevant?
>
> ... what this patch deals with. The answer to your question is "yes",
> also in light of your subsequent replies, albeit I still wouldn't be
> able to tell why things did work for you before.
With your patch applied the domain starts now, regardless of
LIBXL_RDM_RESERVE_POLICY_RELAXED set or not.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-06 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 1:07 [Xen-devel] Broken PCI device passthrough, after XSA-302 fix? Marek Marczykowski-Górecki
2020-01-06 11:18 ` Jan Beulich
2020-01-06 14:04 ` Marek Marczykowski-Górecki
2020-01-06 14:16 ` Marek Marczykowski-Górecki
2020-01-06 14:29 ` Marek Marczykowski-Górecki
2020-01-06 14:38 ` Jan Beulich
2020-01-06 16:37 ` Marek Marczykowski-Górecki [this message]
2020-01-06 13:06 ` Jan Beulich
2020-01-19 10:39 ` Pasi Kärkkäinen
2020-01-20 8:36 ` Jan Beulich
2020-01-20 9:10 ` Pasi Kärkkäinen
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=20200106163731.GM1314@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.