summaryrefslogtreecommitdiffstats
path: root/net/batman-adv
diff options
context:
space:
mode:
authorJuergen Gross <jgross@suse.com>2021-10-22 08:47:56 +0200
committerBoris Ostrovsky <boris.ostrovsky@oracle.com>2021-11-23 13:41:29 -0600
commit37a72b08a3e1eb28053214dd8211eb09c2fd3187 (patch)
tree2e9c964969b4608d467dbfbb8fa16e784d0542f8 /net/batman-adv
parent2a0991929aba0a3dd6fe51d1daba06a93a96a021 (diff)
downloadlinux-stable-37a72b08a3e1eb28053214dd8211eb09c2fd3187.tar.gz
linux-stable-37a72b08a3e1eb28053214dd8211eb09c2fd3187.tar.bz2
linux-stable-37a72b08a3e1eb28053214dd8211eb09c2fd3187.zip
xen: add "not_essential" flag to struct xenbus_driver
When booting the xenbus driver will wait for PV devices to have connected to their backends before continuing. The timeout is different between essential and non-essential devices. Non-essential devices are identified by their nodenames directly in the xenbus driver, which requires to update this list in case a new device type being non-essential is added (this was missed for several types in the past). In order to avoid this problem, add a "not_essential" flag to struct xenbus_driver which can be set to "true" by the respective frontend. Set this flag for the frontends currently regarded to be not essential (vkbs and vfb) and use it for testing in the xenbus driver. Signed-off-by: Juergen Gross <jgross@suse.com> Link: https://lore.kernel.org/r/20211022064800.14978-2-jgross@suse.com Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Diffstat (limited to 'net/batman-adv')
0 files changed, 0 insertions, 0 deletions