From: Jan Beulich <jbeulich@suse.com>
To: Igor Druzhinin <igor.druzhinin@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-kernel@vger.kernel.org, Juergen Gross <jgross@suse.com>
Subject: Re: [Xen-devel] [PATCH] xen/pci: try to reserve MCFG areas earlier
Date: Wed, 11 Sep 2019 11:13:41 +0200 [thread overview]
Message-ID: <65b8d74a-2f7b-a257-a750-9dada5206f01@suse.com> (raw)
In-Reply-To: <74c9d2cc-a528-2cec-099e-0d803aeace6f@citrix.com>
On 11.09.2019 03:15, Igor Druzhinin wrote:
> Another thing that I implied by "not supporting" but want to explicitly
> call out is that currently Xen will refuse reserving any MCFG area
> unless it actually existed in MCFG table at boot. I don't clearly
> understand reasoning behind it but it might be worth relaxing at least
> size matching restriction on Xen side now with this change.
I guess it's because no-one had a system were it would be needed,
and hence could be tested.
Jan
WARNING: multiple messages have this Message-ID (diff)
From: Jan Beulich <jbeulich@suse.com>
To: Igor Druzhinin <igor.druzhinin@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen/pci: try to reserve MCFG areas earlier
Date: Wed, 11 Sep 2019 11:13:41 +0200 [thread overview]
Message-ID: <65b8d74a-2f7b-a257-a750-9dada5206f01@suse.com> (raw)
In-Reply-To: <74c9d2cc-a528-2cec-099e-0d803aeace6f@citrix.com>
On 11.09.2019 03:15, Igor Druzhinin wrote:
> Another thing that I implied by "not supporting" but want to explicitly
> call out is that currently Xen will refuse reserving any MCFG area
> unless it actually existed in MCFG table at boot. I don't clearly
> understand reasoning behind it but it might be worth relaxing at least
> size matching restriction on Xen side now with this change.
I guess it's because no-one had a system were it would be needed,
and hence could be tested.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-09-11 9:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 0:20 [PATCH] xen/pci: try to reserve MCFG areas earlier Igor Druzhinin
2019-09-04 0:20 ` [Xen-devel] " Igor Druzhinin
2019-09-04 9:08 ` Jan Beulich
2019-09-04 9:08 ` [Xen-devel] " Jan Beulich
2019-09-04 11:36 ` Igor Druzhinin
2019-09-04 11:36 ` [Xen-devel] " Igor Druzhinin
2019-09-04 12:09 ` Jan Beulich
2019-09-04 12:09 ` [Xen-devel] " Jan Beulich
2019-09-06 22:30 ` Boris Ostrovsky
2019-09-06 22:30 ` [Xen-devel] " Boris Ostrovsky
2019-09-06 23:00 ` Igor Druzhinin
2019-09-06 23:00 ` [Xen-devel] " Igor Druzhinin
2019-09-08 18:28 ` Boris Ostrovsky
2019-09-08 18:28 ` [Xen-devel] " Boris Ostrovsky
2019-09-08 21:11 ` Igor Druzhinin
2019-09-08 21:11 ` [Xen-devel] " Igor Druzhinin
2019-09-08 23:30 ` Boris Ostrovsky
2019-09-08 23:30 ` [Xen-devel] " Boris Ostrovsky
2019-09-08 23:37 ` Igor Druzhinin
2019-09-08 23:37 ` [Xen-devel] " Igor Druzhinin
2019-09-09 19:19 ` Boris Ostrovsky
2019-09-09 19:19 ` [Xen-devel] " Boris Ostrovsky
2019-09-09 21:48 ` Igor Druzhinin
2019-09-09 21:48 ` [Xen-devel] " Igor Druzhinin
2019-09-10 1:47 ` Boris Ostrovsky
2019-09-10 1:47 ` Boris Ostrovsky
2019-09-10 9:46 ` Igor Druzhinin
2019-09-10 9:46 ` Igor Druzhinin
2019-09-10 9:55 ` Jan Beulich
2019-09-10 9:55 ` Jan Beulich
2019-09-10 10:08 ` Igor Druzhinin
2019-09-10 10:08 ` Igor Druzhinin
2019-09-10 17:48 ` Boris Ostrovsky
2019-09-10 17:48 ` Boris Ostrovsky
2019-09-10 20:36 ` Igor Druzhinin
2019-09-10 20:36 ` Igor Druzhinin
2019-09-10 21:19 ` Boris Ostrovsky
2019-09-10 21:19 ` Boris Ostrovsky
2019-09-11 1:15 ` Igor Druzhinin
2019-09-11 1:15 ` Igor Druzhinin
2019-09-11 9:13 ` Jan Beulich [this message]
2019-09-11 9:13 ` Jan Beulich
2019-09-12 17:33 ` Boris Ostrovsky
2019-09-12 17:33 ` Boris Ostrovsky
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=65b8d74a-2f7b-a257-a750-9dada5206f01@suse.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=igor.druzhinin@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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.