From: Christoph Hellwig <hch@lst.de>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
regressions@lists.linux.dev, dri-devel@lists.freedesktop.org,
"Anshuman Khandual" <anshuman.khandual@arm.com>,
intel-gfx@lists.freedesktop.org,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
iommu@lists.linux.dev, "Matthew Auld" <matthew.auld@intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
xen-devel@lists.xenproject.org, "Christoph Hellwig" <hch@lst.de>
Subject: Re: [Intel-gfx] i915 "GPU HANG", bisected to a2daa27c0c61 "swiotlb: simplify swiotlb_max_segment"
Date: Tue, 18 Oct 2022 13:02:43 +0200 [thread overview]
Message-ID: <20221018110243.GA4655@lst.de> (raw)
In-Reply-To: <a5966644-72d7-4b25-83d1-9765d0593e44@suse.com>
On Tue, Oct 18, 2022 at 10:57:37AM +0200, Jan Beulich wrote:
> Shouldn't this then be xen_pv_domain() that you use here, and - if you
> really want IS_ENABLED() in addition - CONFIG_XEN_PV?
I'll need help from people that understand Xen better than me what
the exact conditions (and maybe also comments are).
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Anshuman Khandual" <anshuman.khandual@arm.com>,
"Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
regressions@lists.linux.dev, xen-devel@lists.xenproject.org,
iommu@lists.linux.dev,
"Robert Beckett" <bob.beckett@collabora.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Matthew Auld" <matthew.auld@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: i915 "GPU HANG", bisected to a2daa27c0c61 "swiotlb: simplify swiotlb_max_segment"
Date: Tue, 18 Oct 2022 13:02:43 +0200 [thread overview]
Message-ID: <20221018110243.GA4655@lst.de> (raw)
In-Reply-To: <a5966644-72d7-4b25-83d1-9765d0593e44@suse.com>
On Tue, Oct 18, 2022 at 10:57:37AM +0200, Jan Beulich wrote:
> Shouldn't this then be xen_pv_domain() that you use here, and - if you
> really want IS_ENABLED() in addition - CONFIG_XEN_PV?
I'll need help from people that understand Xen better than me what
the exact conditions (and maybe also comments are).
next prev parent reply other threads:[~2022-10-18 11:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 3:52 i915 "GPU HANG", bisected to a2daa27c0c61 "swiotlb: simplify swiotlb_max_segment" Marek Marczykowski-Górecki
2022-10-18 8:24 ` [Intel-gfx] " Christoph Hellwig
2022-10-18 8:24 ` Christoph Hellwig
2022-10-18 8:57 ` [Intel-gfx] " Jan Beulich
2022-10-18 8:57 ` Jan Beulich
2022-10-18 8:57 ` Jan Beulich
2022-10-18 11:02 ` Christoph Hellwig [this message]
2022-10-18 11:02 ` Christoph Hellwig
2022-10-18 14:21 ` [Intel-gfx] " Jan Beulich
2022-10-18 14:21 ` Jan Beulich
2022-10-18 14:21 ` Jan Beulich
2022-10-18 14:33 ` [Intel-gfx] " Christoph Hellwig
2022-10-18 14:33 ` Christoph Hellwig
2022-10-18 14:53 ` [Intel-gfx] " Juergen Gross
2022-10-18 14:53 ` Juergen Gross
2022-10-18 14:53 ` Juergen Gross
2022-10-18 14:55 ` [Intel-gfx] " Christoph Hellwig
2022-10-18 14:55 ` Christoph Hellwig
2022-10-18 12:01 ` Marek Marczykowski-Górecki
2022-10-18 12:01 ` Marek Marczykowski-Górecki
2022-10-18 8:31 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
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=20221018110243.GA4655@lst.de \
--to=hch@lst.de \
--cc=anshuman.khandual@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=marmarek@invisiblethingslab.com \
--cc=matthew.auld@intel.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=regressions@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=sstabellini@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.