From: Christoph Hellwig <hch@lst.de>
To: Juergen Gross <jgross@suse.com>
Cc: "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>,
"Jan Beulich" <jbeulich@suse.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 16:55:50 +0200 [thread overview]
Message-ID: <20221018145550.GA21066@lst.de> (raw)
In-Reply-To: <e0448dac-a35e-cfd0-c087-411558512b5e@suse.com>
On Tue, Oct 18, 2022 at 04:53:50PM +0200, Juergen Gross wrote:
>> If we don't need the IS_ENABLED is not needed I'm all for dropping it.
>> But unless I misread the code, on arm/arm64 even PV guests are 1:1
>> mapped so that all Linux physically contigous memory also is Xen
>> contigous, so we don't need the hack.
>
> There are no PV guests on arm/arm64.
Ok, that's the part I was missing. In that case we should be fine
without the IS_ENABLED indeed.
next prev parent reply other threads:[~2022-10-18 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y04i8V7xamTkuqNA@mail-itl>
2022-10-18 8:24 ` [Intel-gfx] i915 "GPU HANG", bisected to a2daa27c0c61 "swiotlb: simplify swiotlb_max_segment" Christoph Hellwig
2022-10-18 8:57 ` Jan Beulich
2022-10-18 11:02 ` Christoph Hellwig
2022-10-18 14:21 ` Jan Beulich
2022-10-18 14:33 ` Christoph Hellwig
2022-10-18 14:53 ` Juergen Gross
2022-10-18 14:55 ` Christoph Hellwig [this message]
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=20221018145550.GA21066@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox