Re: bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible

2020-01-12 Thread Gerd Hoffmann 
On Fri, Jan 10, 2020 at 05:32:11PM +0100, Marek Marczykowski-Górecki wrote:
> Hi,
> 
> This is the context of "bochs_drm: failed bochs_hw_init() results in
> panic". When I boot the system, if plymouth is visible, it crashes. But
> if I press ESC to hide it, it boots fine. bochs_drm is build as module
> and _not_ included in the initramfs, so it is loaded only after root
> filesystem is mounted. And before that, efifb works just fine, including
> nice graphical disk passphrase prompt.

> [   32.951345] fb0: switching to bochsdrmfb from EFI VGA
[ ... ]
> [   33.030158] bochs-drm :00:02.0: BAR 0: can't reserve [mem 
> 0xc000-0xc0ff pref]

Looks like efifb continues to claim the framebuffer resource
(0xc000-0xc0ff) for some reason, so bochs-drm can't
reserve it.

No clue why, also doesn't reproduce here (standard fedora 31 5.4.7
kernel).  I don't have an encrypted disk, so no passphrase prompt,
maybe that makes a difference.

How does /proc/iomem look after boot, specifically the :00:02.0 pci
bars?

cheers,
  Gerd

___
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

Re: bochs_drm: failed bochs_hw_init() results in panic

2020-01-12 Thread Gerd Hoffmann 
> Now the messages looks like this:
> 
> [   29.800835] bochs-drm :00:02.0: remove_conflicting_pci_framebuffers: 
> bar 0: 0xc000 -> 0xc0ff
> [   29.800840] bochs-drm :00:02.0: remove_conflicting_pci_framebuffers: 
> bar 2: 0xc1087000 -> 0xc1087fff
> [   29.800842] checking generic (c000 100) vs hw (c000 100)
> [   29.800843] fb0: switching to bochsdrmfb from EFI VGA
> [   29.805542] bochs-drm :00:02.0: vgaarb: deactivate vga console
> [   29.805742] bochs-drm :00:02.0: BAR 0: can't reserve [mem 
> 0xc000-0xc0ff pref]
> [   29.805749] [drm:bochs_hw_init [bochs_drm]] *ERROR* Cannot request 
> framebuffer

This is the problem.

> [   29.805781] bochs-drm: probe of :00:02.0 failed with error -16
> [   30.129014] Trying to free nonexistent resource 
> 
> 
> Is the last one an issue?

Not critical.  Probably the pci_release_regions() call, trying to free
all regions, including the one the driver could not request, so it warns
about that one.

cheers,
  Gerd

___
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

Re: [PATCH] drm/cirrus: Let DRM core send VBLANK events

2020-01-12 Thread Daniel Vetter 
On Fri, Jan 10, 2020 at 12:57:07PM +0100, Thomas Zimmermann wrote:
> In drm_atomic_helper_fake_vblank() the DRM core sends out VBLANK
> events if struct drm_crtc_state.no_vblank is enabled. Replace cirrus'
> VBLANK events with the DRM core's functionality.
> 
> Signed-off-by: Thomas Zimmermann 
> ---
>  drivers/gpu/drm/cirrus/cirrus.c | 10 ++
>  1 file changed, 2 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/gpu/drm/cirrus/cirrus.c b/drivers/gpu/drm/cirrus/cirrus.c
> index 248c9f765c45..4a1729aa7e53 100644
> --- a/drivers/gpu/drm/cirrus/cirrus.c
> +++ b/drivers/gpu/drm/cirrus/cirrus.c
> @@ -38,7 +38,6 @@
>  #include 
>  #include 
>  #include 
> -#include 
>  
>  #define DRIVER_NAME "cirrus"
>  #define DRIVER_DESC "qemu cirrus vga"
> @@ -415,6 +414,8 @@ static void cirrus_pipe_enable(struct 
> drm_simple_display_pipe *pipe,
>  {
>   struct cirrus_device *cirrus = pipe->crtc.dev->dev_private;
>  
> + crtc_state->no_vblank = true;

Huh, nice untended use of this stuff ... We've added this for writeback,
but I guess it can be used for anything that's a virtual connector ...

I've also spotted that you've done this same trick for ast & udl already.
But I think before we roll this out massively we should make this
official. Can you pls do a patch to update the kerneldoc for @no_vblank
that virtual hw can also use this stuff?

Also, computing state values in atomic_commit code is kinda uncool and
fraught with peril - design assumption is that with some very few
exceptions (which are kinda awkward, would be nice to make state pointers
const) all the core and helper codes that state structures stay unchanged
after atomic_check completed. This should be computed in atomic_check (like vc4
does). Can you pls also include patches to update ast and udl in this
series?

Thanks, Daniel


> +
>   cirrus_mode_set(cirrus, &crtc_state->mode, plane_state->fb);
>   cirrus_fb_blit_fullscreen(plane_state->fb);
>  }
> @@ -434,13 +435,6 @@ static void cirrus_pipe_update(struct 
> drm_simple_display_pipe *pipe,
>  
>   if (drm_atomic_helper_damage_merged(old_state, state, &rect))
>   cirrus_fb_blit_rect(pipe->plane.state->fb, &rect);
> -
> - if (crtc->state->event) {
> - spin_lock_irq(&crtc->dev->event_lock);
> - drm_crtc_send_vblank_event(crtc, crtc->state->event);
> - crtc->state->event = NULL;
> - spin_unlock_irq(&crtc->dev->event_lock);
> - }
>  }
>  
>  static const struct drm_simple_display_pipe_funcs cirrus_pipe_funcs = {
> -- 
> 2.24.1
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
___
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

CISTI'2020 - Doctoral Symposium | Seville, Spain; Deadline: February 14

2020-01-12 Thread Maria Lemos 
* Published in IEEE Xplore and indexed by ISI, Scopus, EI-Compendex, Google 
Scholar, etc.

** Conference with H5-Index = 16 (Google Scholar Ranking)


---
Doctoral Symposium of CISTI'2020 - 15th Iberian Conference on Information 
Systems and Technologies
   Seville, Spain, 24 - 27 June 
2020
   
http://www.cisti.eu/ 


 

The purpose of CISTI'2020’s Doctoral Symposium is to provide graduate students 
a setting where they can, informally, expose and discuss their work, collecting 
valuable expert opinions and sharing new ideas, methods and applications. The 
Doctoral Symposium is an excellent opportunity for PhD students to present and 
discuss their work in a Workshop format. Each presentation will be evaluated by 
a panel composed by at least three Information Systems and Technologies experts.

 

Contributions Submission

The Doctoral Symposium is opened to PhD students whose research area includes 
the themes proposed for this Conference. Submissions must include an extended 
abstract (maximum 4 pages), following the Conference style guide 
. All selected contributions will be 
published with the Conference Proceedings in electronic format with ISBN. These 
contributions will be available in the IEEE Xplore 
 Digital Library 
and will be sent for indexing in ISI, Scopus, EI-Compendex, INSPEC and Google 
Scholar.

Submissions must include the field, the PhD institution and the number of 
months devoted to the development of the work. Additionally, they should 
include in a clear and succinct manner:

•The problem approached and its significance or relevance
•The research objectives and related investigation topics
•A brief display of what is already known
•A proposed solution methodology for the problem
•Expected results

 

Important Dates

Paper submission: February 14, 2020

Notification of acceptance: March 22, 2020

Submission of accepted papers: April 5, 2020

Payment of registration, to ensure the inclusion of an accepted paper in the 
conference proceedings: April 5, 2020

 

Organizing Committee


Álvaro Rocha, Universidade de Coimbra

Francisco García-Peñalvo, Universidad de Salamanca

 

Scientific Committee

Francisco García-Peñalvo, Universidad de Salamanca (Chair)

Adérito Marcos, Universidade Aberta

Adolfo Lozano Tello, Universidad de Extremadura

Álvaro Rocha, Universidade de Coimbra

Ana Amélia Carvalho, Universidade de Coimbra

Ana Maria Ramalho Correia, NOVA IMS

Antonio Fernández-Caballero, Universidad de Castilla-La Mancha

Antonio Garcia-Loureiro, Universidad de Santiago de Compostela

Arnaldo Martins, Universidade de Aveiro

Bráulio Alturas, ISCTE - Insituto Universitário de Lisboa

Carlos Costa, ISEG, Universidade de Lisboa

Carlos Ferrás Sexto, Universidad de Santiago de Compostela

Carlos Juiz, Universitat de les Illes Balears

David Fonseca, La Salle, Universitat Ramon Llull

Ernest Redondo, Universidad Politécnica de Catalunya

Feliz Gouveia, Universidade Fernando Pessoa

Fernando Moreira, Universidade Portucalense

Fernando Ramos, Universidade de Aveiro

Francisco Restivo, Universidade Católica Portuguesa

Gonçalo Paiva Dias, Universidade de Aveiro

Gonzalo Cuevas Agustin, Universidad Politécnica de Madrid

Jesús Fraile Ardanuy, Universidad Politécnica de Madrid

João Costa, Universidade de Coimbra

José Antonio Calvo-Manzano Villalón, Universidad Politécnica de Madrid

José Borbinha, IST, Universidade de Lisboa

Jose M. Molina, Universidad Carlos III de Madrid

Jose Machado, Universidade do Minho

João Manuel R.S. Tavares, FEUP, Universidade do Porto

José Martins, Universidade de Trás-os-Montes e Alto Douro

Luis Camarinha-Matos, Universidade Nova de Lisboa

Luís Paulo Reis, FEUP, Universidade do Porto

Manuel Pérez Cota, Universidad de Vigo

Marco Painho, NOVA IMS

Mário Piattini, Universidad de Castilla-La Mancha

Martin Llamas Nistal, Universidad de Vigo

Miguel Ramón González Castro, Ence, Energía y Celulosa

Nelson Rocha, Universidade de Aveiro

Óscar Mealha, Universidade de Aveiro

Paulo Pinto, FC, Universidade Nova de Lisboa

Pedro Sánchez-Palma, Universidad Politécnica de Cartagena

Pilar Mareca, Universidad Politécnica de Madrid

Ramiro Gonçalves, Universidade de Trás-os-Montes e Alto Douro

Vitor Santos, NOVA IMS


 

CISTI'2020 webpage:  http://www.cisti.eu/ 


Kind regards,

CISTI'2020 Team
http://www.cisti.eu/ 



 


PS: If you do not wish to receive more notices from AISTI (http://www.aisti.eu