[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [Question] Proper location for Linux error code (-EPROBE_DEFER) in Xen
- To: Oleksandr <olekstysh@xxxxxxxxx>
- From: Jan Beulich <JBeulich@xxxxxxxx>
- Date: Thu, 1 Aug 2019 14:34:05 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=suse.com;dmarc=pass action=none header.from=suse.com;dkim=pass header.d=suse.com;arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5oexHWcBZ3fjkw+si60HJ1mhC/TI1puqMAw7Z/pO2KA=; b=OEWddd6gc06dWy1Hv1iplgiBUdoPtmBxav5YZB4MeRu9yeTSmgIxDtkrpY43IyaI2eP8ZrGQZ0n2zGJG81wmC7yjQWlgKNsvZwCQFK5Z27gnL+V9Q5qb0Jd+NKGoAkPhJnac6EtLaSK4ekWu7Nrq60QBNRSeeDcTowVOjcivZ7qEmwlDWEzfw8xC9QWuhctudu4cjNp/M9is7zGnvOjLDsXPMHfplra8C5SJKm3CCHtYYQGxNU7PAzG199BqAfukeXXpICJQA8eYeq8PctlBklbYDJjQqPUW+QruTcS0DxmlFea5/Sh1l7Yv8UrWRAoSgoeFrtFwpAUkuFcrwwhY7g==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UOzP7JOSAUBAnu1ztyZb9fJzpjVv4QpI6WRIzpE2Rjt0VXBBHs0L8XQiEDVAPRFZpNyg7k3l0is7ewBVrSgO2rCqI4IAgCYZlorWnKJPuIQ/+z4I1iuNEZpxWGwz60wGgdac/epYfCwZ5CSzA2XZ308Sk42bHAg/V33pn9n4dv5Luz7TPp5yiMqAndzc2F+cR032oNjOK5t2smi/CPN1CaHn2utE84pA49IoPIWD/AMlo0fd4F+MDgwKOgivQwewT2k0m7CDqrVfkStn1oqRghev+cK3wCgmg9ADmF+6GnrVhUeFCy03FU5NOwrzrXUGGtRtptPAk6DIdGArUiSRAg==
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=JBeulich@xxxxxxxx;
- Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Delivery-date: Thu, 01 Aug 2019 14:35:40 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AQHVSHMGyAlemcbWoE2ESYTmEuHFv6bmVsbbgAAEHCWAAACGAA==
- Thread-topic: [Xen-devel] [Question] Proper location for Linux error code (-EPROBE_DEFER) in Xen
On 01.08.2019 16:31, Oleksandr wrote:
> This is needed for the upcoming V2 of the IPMMU driver (ARM) [1] which may
> request
> deferred probing (returns -EPROBE_DEFER) depending on what device will be
> probed the first
> (Root device must be registered before Cache devices. If not the case,
> driver will deny further Cache device probes until Root device is
> registered).
>
> As we can't guarantee a fixed pre-defined order for the device nodes in DT,
> we need to be ready for the situation where devices being probed
> in "any" order. So, framework (drivers/passthrough/arm/iommu.c) will be
> modified a bit to be able to handle -EPROBE_DEFER returning by driver.
I'm sure this can be had without introducing a new error code.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
