Re: PCI arbiter crash on last qemu image

From	Joan Lledó <jlledom@mailfence.com>
Newsgroups	gnu.hurd.bug
Subject	Re: PCI arbiter crash on last qemu image
Date	2020-08-17 22:51 +0200
Message-ID	<mailman.96.1597697504.2469.bug-hurd@gnu.org> (permalink)
References	<78d17df2-64dd-692e-4151-ad14e25a97d6@mailfence.com> <2f03cf83-9dff-1b92-a6e0-96ae20bfda49@zamaudio.com> <e3d57b71-af84-c035-7799-0c4dc6bfdae4@mailfence.com> <c5ae2597-dd25-58f6-8aa2-18b60b91fe5f@zamaudio.com> <ce86a983-886d-cf4d-bb44-106a17ad9282@mailfence.com>

Show all headers | View raw

El 17/8/20 a les 1:51, Damien Zammit ha escrit:
> It's probably due to this patch:

It's surely for that

> Perhaps a better way to fix the mapping problem I encountered
> is by removing the check for previous mappings when trying to map regions,

I could check the pointer before reading from it at func_files.c, and if
it happens to be null, then call the libpciaccess mapping function from
there, i.e. mapping the memory in the first access instead of doing it
during the startup. So there's no need to make any changes in your
patch, do you think that'd work?

Back to gnu.hurd.bug | Previous | Next | Find similar

Thread

Re: PCI arbiter crash on last qemu image Joan Lledó <jlledom@mailfence.com> - 2020-08-17 22:51 +0200

csiph-web